Date: Sun, 26 Nov 2006 10:29:32 +0100 From: "[LoN]Kamikaze" <LoN_Kamikaze@gmx.de> To: Mark <admin@asarian-host.net> Cc: freebsd-questions@freebsd.org Subject: Re: GCC upgrade Message-ID: <45695E7C.8040006@gmx.de> In-Reply-To: <200611260905.kAQ95BcY091634@asarian-host.net> References: <200611260905.kAQ95BcY091634@asarian-host.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Mark wrote:
> One question, though:
>
> ..if ${.CURDIR:M*/ports/*} && !${.CURDIR:M*/work/*}
>
> Why would you NOT want to use the new gcc when in a /work/ directory?
> (where ports builds).
>
> Thanks,
>
> - Mark
This is because these settings are processed in the ports framework and overwriting whatever became of them in the process by applying them to make calls from the working directory might break something.
By the way (inserting shameless advertisement), if you find the make syntax clumsy for configuring ports and portsconf too restrictive, you might want to have a look at buildflags from the sysutils/bsdadminscripts ports. It offers a more compact syntax (that actually will be parsed into make syntax) and certain knobs, that make handling several compilers, ccache, distcc and parallel building '-j' easier.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45695E7C.8040006>