Date: Mon, 28 Apr 2014 08:23:34 -0600 From: Ian Lepore <ian@FreeBSD.org> To: Julian Elischer <julian@FreeBSD.org> Cc: FreeBSD Current <current@FreeBSD.org> Subject: Re: options for forcing use of GCC Message-ID: <1398695014.61646.212.camel@revolution.hippie.lan> In-Reply-To: <535E5FA0.9050703@freebsd.org> References: <535D1350.4000106@freebsd.org> <1398616234.61646.155.camel@revolution.hippie.lan> <535DFB11.4020904@freebsd.org> <1398686749.61646.203.camel@revolution.hippie.lan> <535E5FA0.9050703@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 2014-04-28 at 22:03 +0800, Julian Elischer wrote: > On 4/28/14, 8:05 PM, Ian Lepore wrote: > > On Mon, 2014-04-28 at 14:54 +0800, Julian Elischer wrote: > >> On 4/28/14, 12:30 AM, Ian Lepore wrote: > >>> WITH_GCC=yes \ > >>> WITH_GNUCXX=yes \ > >>> WITHOUT_CLANG=yes \ > >>> WITHOUT_CLANG_IS_CC=yes \ > >> forgot to ask.. is this in /etc/make.conf? > >> or elsewhere? > > Actually in our build system we build in a chroot, and we inject those > > args into the environment during the builds so that we can have > > different options for building world versus cross-world within the > > chroot, but I think the more-normal place would be make.conf. > > we also use a combination of environment and make.conf in a chroot. > though people sometimes talk about a src.conf (or is that src.mk?) but > I haven't found that one yet. > > > > -- Ian > > > > > > In theory, /etc/make.conf affects all builds you do -- world, kernel, ports, your own apps, everything -- whereas /etc/src.conf affects only kernel and world. I've heard it said that the reality falls short of that and src.conf settings inappropriately leak into ports builds. -- Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1398695014.61646.212.camel>