From owner-freebsd-current@FreeBSD.ORG Tue Apr 29 00:39:03 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 C03E1768 for ; Tue, 29 Apr 2014 00:39:03 +0000 (UTC) Received: from mail-pb0-f48.google.com (mail-pb0-f48.google.com [209.85.160.48]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 91DA91665 for ; Tue, 29 Apr 2014 00:39:03 +0000 (UTC) Received: by mail-pb0-f48.google.com with SMTP id md12so6482270pbc.35 for ; Mon, 28 Apr 2014 17:39:03 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=M/DiahlfCczm5PARJmbeFk7fwkADQOAf/Oo+eiNDyks=; b=E4lFC3Dm6lOOlO5go35+4y6BJfExEmFsWj6VC/kQTgsVGTWzmD/haoj+KpzbilcIC4 QE6dTCtuQUUEJhZmE5d9CHA2RK3pJk+fRadInGLI990M4LZX4zhTKsuvTctTSaVnpj3l 4pk6pSzL0GCFIyfdPuJyh9O4h6i5FbRDufEWJevgfMD1Yee2fA5utk3fKYzJXkySOBBT 1k5okMstH24mjtCxL04LNogaJMiYPzE8nKX5+A0qnWj+zZJQnPQN6yNcumxUeuuNhslu aYKCwRSgLUzFbkdPlT81Y6GUyJEkZ8kYPalqdb7/eMbLPdBERJZLZ+fNRnClISGLqgQw 17wg== X-Gm-Message-State: ALoCoQnkYLypNQwZAl+5sjNP+wnTP8PZbwm8ihddTjF8XpUKnam/jmX8Vx+5LrHwj9DFE4tyydpX X-Received: by 10.68.240.68 with SMTP id vy4mr12510070pbc.127.1398731942796; Mon, 28 Apr 2014 17:39:02 -0700 (PDT) Received: from [10.64.26.118] (dc1-prod.netflix.com. [69.53.236.251]) by mx.google.com with ESMTPSA id xk3sm37671083pbb.65.2014.04.28.17.39.01 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 28 Apr 2014 17:39:02 -0700 (PDT) Sender: Warner Losh X-Google-Original-From: Warner Losh Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) Subject: Re: options for forcing use of GCC From: Warner Losh In-Reply-To: <1398616234.61646.155.camel@revolution.hippie.lan> Date: Mon, 28 Apr 2014 18:38:59 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <5BC3D326-94DE-4438-98B9-1A6C3542F08E@gmail.com> References: <535D1350.4000106@freebsd.org> <1398616234.61646.155.camel@revolution.hippie.lan> To: Ian Lepore X-Mailer: Apple Mail (2.1874) 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: Tue, 29 Apr 2014 00:39:03 -0000 On Apr 27, 2014, at 10: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=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=