320b032dff014ca7817aa92b021702da87f44770
two gmakes were descending into `engines' directory at the save time:
===> Building for yate-4.3.0.p1
c++ -Wall -I. -I. -O2 -pipe -fPIC [...] -c main.cpp
gmake -C ./engine all
gmake -C ./engine all
gmake[1]: Entering directory `[...]/yate-4.3.0-1/engine'
As a result of this, produced `libyate.so.4.3.0' can be bogus, and will
fail to link against:
c++ -Wall -L/usr/local/lib -o yate -lpthread main.o libyate.so
libyate.so: undefined reference to
`TelEngine::DefaultLogic::DefaultLogic(char const*, int)'
libyate.so: undefined reference to
`TelEngine::ClientLogic::initStaticData()'
gmake: *** [yate] Error 1
To mitigate the problem, avoid dependency on phony `library' target, but
define build command for real libyate.so.4.3.0, and use it as dependency
instead.
- While here, adopt the new LIB_DEPENDS syntax, convert USE_GMAKE
- Drop GNU_CONFIGURE, implied by USE_AUTOTOOLS; sort the knobs a bit
- Do not overwrite few options' descriptions we have from the pool
- Pad the output when displaying pkg-message (by consistent with package)
…
…
…
This is the FreeBSD Ports Collection. For an easy to use WEB-based interface to it, please see: http://www.FreeBSD.org/ports For general information on the Ports Collection, please see the FreeBSD Handbook ports section which is available from: http://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: http://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.
Description
Languages
Makefile
59.7%
C
16.1%
Shell
7.2%
Roff
5%
C++
3.7%
Other
7%