c++ -O2 -pipe -fstack-protector-strong -fno-strict-aliasing -I../../include -Iposix -I../core/posix -c -o activity_statistics_monitor.o activity_statistics_monitor.cpp
In file included from activity_statistics_monitor.cpp:18:
In file included from ./incoming_message.h:20:
In file included from ./parameters.h:20:
In file included from ./parameter_entry.h:24:
In file included from /usr/include/c++/v1/string:506:
In file included from /usr/include/c++/v1/string_view:175:
In file included from /usr/include/c++/v1/__string:57:
In file included from /usr/include/c++/v1/algorithm:643:
In file included from /usr/include/c++/v1/memory:681:
In file included from /usr/include/c++/v1/atomic:571:
/usr/include/c++/v1/__threading_support:76:9: error: unknown type name 'sem_t'
typedef sem_t __libcpp_semaphore_t;
^
Reported by: pkg-fallout
MFH: 2021Q1
This is the FreeBSD Ports Collection. For an easy to use
WEB-based interface to it, please see:
https://www.FreeBSD.org/ports
For general information on the Ports Collection, please see the
FreeBSD Handbook ports section which is available from:
https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/ports.html
for the latest official version
or:
The ports(7) manual page (man ports).
These will explain how to use ports and packages.
If you would like to search for a port, you can do so easily by
saying (in /usr/ports):
make search name="<name>"
or:
make search key="<keyword>"
which will generate a list of all ports matching <name> or <keyword>.
make search also supports wildcards, such as:
make search name="gtk*"
For information about contributing to FreeBSD ports, please see the Porter's
Handbook, available at:
https://www.FreeBSD.org/doc/en_US.ISO8859-1/books/porters-handbook/
NOTE: This tree will GROW significantly in size during normal usage!
The distribution tar files can and do accumulate in /usr/ports/distfiles,
and the individual ports will also use up lots of space in their work
subdirectories unless you remember to "make clean" after you're done
building a given port. /usr/ports/distfiles can also be periodically
cleaned without ill-effect.
81febe9031