From owner-freebsd-current@FreeBSD.ORG Sun Apr 27 14:25:45 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 0CD6BC52 for ; Sun, 27 Apr 2014 14:25:45 +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 B9D751947 for ; Sun, 27 Apr 2014 14:25:44 +0000 (UTC) Received: from Julian-MBP3.local (50-196-156-133-static.hfc.comcastbusiness.net [50.196.156.133]) (authenticated bits=0) by vps1.elischer.org (8.14.8/8.14.8) with ESMTP id s3REPPVw064670 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Sun, 27 Apr 2014 07:25:33 -0700 (PDT) (envelope-from julian@freebsd.org) Message-ID: <535D1350.4000106@freebsd.org> Date: Sun, 27 Apr 2014 22:25:20 +0800 From: Julian Elischer 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: FreeBSD Current Subject: options for forcing use of GCC Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 14:25:45 -0000 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