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)
It brings bison as a build dependency in case it is set the following way:
USES= bison or USES= bison:build
it brings bison as a run dependency in case it is set the following way:
USES= bison:run
it brings bison both as a run and build dependency in case it the set the following way:
USES= bison:both
While here trim some headers
Convert some USE_GNOME= gnomehack to USES= pathfix
- disable dahdi
- New port options: Stream Control Transmission Protocol, AMR Narrow Band encoder (opencore), iLBC codec
PR: ports/164398
Approved by: gabor (mentor)
literal name_enable wherever possible, and ${name}_enable
when it's not, to prepare for the demise of set_rcvar().
In cases where I had to hand-edit unusual instances also
modify formatting slightly to be more uniform (and in
some cases, correct). This includes adding some $FreeBSD$
tags, and most importantly moving rcvar= to right after
name= so it's clear that one is derived from the other.
net/yate-devel as net/yate already existed in the repository.
- register in UIDs/GIDs (uses same UID/GID as yate-devel)
PR: ports/156248
Submitted by: Valeriy Komaorv <komarov@valerka.net>
