From owner-freebsd-current@FreeBSD.ORG Mon Apr 28 12:03:35 2014 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E0FECB4; Mon, 28 Apr 2014 12:03:35 +0000 (UTC) Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B4BB2139A; Mon, 28 Apr 2014 12:03:35 +0000 (UTC) Received: from c-24-8-230-52.hsd1.co.comcast.net ([24.8.230.52] helo=damnhippie.dyndns.org) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1WekHV-000NKY-R9; Mon, 28 Apr 2014 12:03:33 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id s3SC3Tqd014935; Mon, 28 Apr 2014 06:03:29 -0600 (MDT) (envelope-from ian@FreeBSD.org) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 24.8.230.52 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX19OwmbADzNZaa6i7YVFlk5R Subject: Re: options for forcing use of GCC vs CLANG From: Ian Lepore To: Julian Elischer , Warner Losh In-Reply-To: <535DF978.9090102@freebsd.org> References: <535D1350.4000106@freebsd.org> <1398616234.61646.155.camel@revolution.hippie.lan> <535DF978.9090102@freebsd.org> Content-Type: text/plain; charset="us-ascii" Date: Mon, 28 Apr 2014 06:03:29 -0600 Message-ID: <1398686609.61646.200.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Apr 2014 12:03:35 -0000 On Mon, 2014-04-28 at 14:47 +0800, Julian Elischer wrote: > On 4/28/14, 12:30 AM, Ian Lepore 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. > > > > -- Ian > > > > > > > > > > Thanks Ian. > Can soneone who is driving this please chime in? I will need to keep > GCC on systems from 9.0 to 10.1 (and various points in between on the > -current lineage). Will the lines above work for that whole range? or > did it change over time? > I expect to flip the CLANG switch sometime around the time when we > slide on to 10.1 or so. > Adding Warner, since he's the one doing the work on this stuff. -- Ian