Date: Mon, 28 Apr 2014 18:38:59 -0600 From: Warner Losh <imp@bsdimp.com> To: Ian Lepore <ian@FreeBSD.org> Cc: FreeBSD Current <current@FreeBSD.org> Subject: Re: options for forcing use of GCC Message-ID: <5BC3D326-94DE-4438-98B9-1A6C3542F08E@gmail.com> In-Reply-To: <1398616234.61646.155.camel@revolution.hippie.lan> References: <535D1350.4000106@freebsd.org> <1398616234.61646.155.camel@revolution.hippie.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
On Apr 27, 2014, at 10:30 AM, Ian Lepore <ian@FreeBSD.org> wrote: > On Sun, 2014-04-27 at 22:25 +0800, Julian Elischer wrote: >> I need to hold off using CLANG for a while at $JOB. We are moving to = a=20 >> newer FBSD in the vicinity of 10.0 but we need to keep the gcc in hte=20= >> picture for a bit longer before switching. What options do I put = into=20 >> various /etc/make.conf to keep CLANG out ofhte picture until we are=20= >> ready for it? >>=20 >> =46rom reading various posts I see: >> WITHOUT_CLANG=3D"yes" >> CC=3Dgcc >> CXX=3Dg++ >> CPP=3Dgcc -E >> but that doesn't seem complete to me. >>=20 >> For now I want to not compile clang in our official build = environment. >> (and obviously not use it until we are ready for it later this year.) >>=20 >> What other hooks do I need to set? >>=20 >> Julian >=20 > We've got the same situation at work. What I'm using right now to = build > 11-current @ r264151 is this: >=20 > WITH_GCC=3Dyes \ > WITH_GNUCXX=3Dyes \ > WITHOUT_CLANG=3Dyes \ > WITHOUT_CLANG_IS_CC=3Dyes \ >=20 > But that's now several weeks out of date, and there are two new knobs = I > haven't investigated yet: WITH_CLANG_BOOTSTRAP and WITH_GCC_BOOTSTRAP. Just to be clear, you=92ll need WITHOUT_CLANG_BOOTSTRAP and = WITH_GCC_BOOTSTRAP for -current, but not -stable. Warner=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5BC3D326-94DE-4438-98B9-1A6C3542F08E>