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 p...@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. _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
