Date: Thu, 13 Oct 2005 06:25:40 +1000 (EST) From: Bruce Evans <bde@zeta.org.au> To: John Baldwin <jhb@FreeBSD.org> Cc: yar@FreeBSD.org, src-committers@FreeBSD.org, cvs-src@FreeBSD.org, cvs-all@FreeBSD.org, ru@FreeBSD.org, Garance A Drosehn <gad@FreeBSD.org> Subject: Re: cvs commit: src/usr.bin/make make.1 Message-ID: <20051013061755.L75612@delplex.bde.org> In-Reply-To: <200510121440.15780.jhb@freebsd.org> References: <200510121009.j9CA9aE3026075@repoman.freebsd.org> <20051012170509.GH99170@submonkey.net> <p06230905bf72f8f32a3b@[128.113.24.47]> <200510121440.15780.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 12 Oct 2005, John Baldwin wrote: > On Wednesday 12 October 2005 02:07 pm, Garance A Drosehn wrote: >> At 6:05 PM +0100 10/12/05, Ceri Davies wrote: >>> On Wed, Oct 12, 2005, Warner Losh wrote: >>> > From: Ruslan Ermilov <ru@freebsd.org> >>> > >>> >> __MAKE_CONF doesn't fall under "make sets or knows about the >>> >> following internal variables or environment variables". >> >> Seems to me that it does. I think the detailed description could > make(1) does not include it. sys.mk does, and it doesn't include it if %POSIX > is defined: > make(1) does honor some special environment variables like MAKEOBJDIRPREFIX, > but __MAKE_CONF is not one of them. It is handled in sys.mk, not in the > make(1) program itself. Also, make -m cause the default sys.mk to not be used. This is the non-hackish way of extending or otherwise altering sys.mk. E.g., to extend it, use a sys.mk that includes the default one after fixing the pollution in it, then add extensions. make -m is actually a usual case under FreeBSD, since buildworld doesn't use the host sys.mk. Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051013061755.L75612>