From owner-freebsd-current@FreeBSD.ORG Sun Apr 27 16:46:57 2014 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0D9A35B9; Sun, 27 Apr 2014 16:46:57 +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 D65139A4; Sun, 27 Apr 2014 16:46:56 +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 1WeRyP-0009Uh-D5; Sun, 27 Apr 2014 16:30:37 +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 s3RGUYwm013995; Sun, 27 Apr 2014 10:30:34 -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: U2FsdGVkX1+VZhHPoFaTBIb4zx/BmN3f Subject: Re: options for forcing use of GCC From: Ian Lepore To: Julian Elischer In-Reply-To: <535D1350.4000106@freebsd.org> References: <535D1350.4000106@freebsd.org> Content-Type: text/plain; charset="us-ascii" Date: Sun, 27 Apr 2014 10:30:34 -0600 Message-ID: <1398616234.61646.155.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: Sun, 27 Apr 2014 16:46:57 -0000 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