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>
index | next in thread | previous in thread | raw e-mail
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 >> newer FBSD in the vicinity of 10.0 but we need to keep the gcc in hte >> picture for a bit longer before switching. What options do I put into >> various /etc/make.conf to keep CLANG out ofhte picture until we are >> ready for it? >> >> From reading various posts I see: >> WITHOUT_CLANG="yes" >> CC=gcc >> CXX=g++ >> CPP=gcc -E >> but that doesn't seem complete to me. >> >> 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.) >> >> What other hooks do I need to set? >> >> Julian > > We've got the same situation at work. What I'm using right now to build > 11-current @ r264151 is this: > > WITH_GCC=yes \ > WITH_GNUCXX=yes \ > WITHOUT_CLANG=yes \ > WITHOUT_CLANG_IS_CC=yes \ > > 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’ll need WITHOUT_CLANG_BOOTSTRAP and WITH_GCC_BOOTSTRAP for -current, but not -stable. Warnerhelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5BC3D326-94DE-4438-98B9-1A6C3542F08E>