Ports, bsd.lib.mk and NOPROFILE
phk at phk.freebsd.dk
Sat Jan 19 01:45:39 UTC 2013
I just tried to build a system with -CURRENT from scratch, and it fell over
in graphics/gd because NOPROFILE is now named NO_PROFILE in bsd.lib.mk
grep(1) tells me that a number of other ports will also have this problem
It may be appropriate with a bandaid in bsd.lib.mk, which emits a noisy
warning, until all these ports are fixed.
A good grep strategy is to look for files containing "NOPROFILE" and
"bsd.lib.mk" but they need not be on the same line.
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
phk at FreeBSD.ORG | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
More information about the freebsd-ports