Date: Fri, 25 Feb 2011 13:13:09 +1100 (EST) From: Bruce Evans <brde@optusnet.com.au> To: Colin Percival <cperciva@FreeBSD.org> Cc: freebsd-bugs@FreeBSD.org, FreeBSD-gnats-submit@FreeBSD.org, Bruce Evans <brde@optusnet.com.au> Subject: Re: bin/155000: make(1) doesn't handle .POSIX: correctly Message-ID: <20110225130750.L892@besplex.bde.org> In-Reply-To: <4D66ECBF.7080900@freebsd.org> References: <20110224112657.38420.qmail@xps.daemonology.net> <20110225093104.W1474@besplex.bde.org> <4D66ECBF.7080900@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 24 Feb 2011, Colin Percival wrote: > On 02/24/11 14:35, Bruce Evans wrote: >> Except that there is the opportunity to set %POSIX using make -D. This >> might be enough in practice. The namespace pollution avoidance is >> too perfect -- there seems to be no way to set %POSIX or .POSIX in the >> environment. > > Is this relevant? POSIX says that the Right Way to demand POSIX mode is > to put .POSIX on the first non-comment line of the Makefile; our %POSIX > variable is a red herring as far as POSIX is concerned. It allows A Way. Of course you should fix make(1) to support the POSIX way if this is not too hard. If make can see .POSIX before including sys.mk, then it could alternatively include a POSIX-sys.mk instead. This would be cleaner than the ifdefs in sys.mk, and would inhibit breakage of the POSIX case by putting things like CTF in its rules. Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110225130750.L892>