From owner-freebsd-current@FreeBSD.ORG  Mon Apr 28 06:47:32 2014
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 1E21DD7F;
 Mon, 28 Apr 2014 06:47:32 +0000 (UTC)
Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "vps1.elischer.org",
 Issuer "CA Cert Signing Authority" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id E42DD11C9;
 Mon, 28 Apr 2014 06:47:31 +0000 (UTC)
Received: from Julian-MBP3.local (gw2.metromesh.com.au [110.5.117.243])
 (authenticated bits=0)
 by vps1.elischer.org (8.14.8/8.14.8) with ESMTP id s3S6lQ2u067144
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO);
 Sun, 27 Apr 2014 23:47:29 -0700 (PDT)
 (envelope-from julian@freebsd.org)
Message-ID: <535DF978.9090102@freebsd.org>
Date: Mon, 28 Apr 2014 14:47:20 +0800
From: Julian Elischer <julian@freebsd.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
 rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Ian Lepore <ian@FreeBSD.org>
Subject: Re: options for forcing use of GCC vs CLANG
References: <535D1350.4000106@freebsd.org>
 <1398616234.61646.155.camel@revolution.hippie.lan>
In-Reply-To: <1398616234.61646.155.camel@revolution.hippie.lan>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: FreeBSD Current <current@FreeBSD.org>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Apr 2014 06:47:32 -0000

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.