From owner-freebsd-ports@FreeBSD.ORG Wed Dec 19 00:18:29 2012 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9D87093D for ; Wed, 19 Dec 2012 00:18:29 +0000 (UTC) (envelope-from kamikaze@bsdforen.de) Received: from mail.server1.bsdforen.de (bsdforen.de [82.193.243.81]) by mx1.freebsd.org (Postfix) with ESMTP id 553298FC15 for ; Wed, 19 Dec 2012 00:18:28 +0000 (UTC) Received: from mobileKamikaze.norad (HSI-KBW-134-3-231-194.hsi14.kabel-badenwuerttemberg.de [134.3.231.194]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.server1.bsdforen.de (Postfix) with ESMTPSA id F064B861C6; Wed, 19 Dec 2012 01:18:21 +0100 (CET) Message-ID: <50D107CC.4050903@bsdforen.de> Date: Wed, 19 Dec 2012 01:18:20 +0100 From: Dominic Fandrey User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Beeblebrox Subject: Re: gcc and g++ version setting in buildflags.conf References: <1355642781949-5769675.post@n5.nabble.com> In-Reply-To: <1355642781949-5769675.post@n5.nabble.com> X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ascii Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Dec 2012 00:18:29 -0000 On 16/12/2012 08:26, Beeblebrox wrote: > I am running a purely clang world (no gcc42), while I also have gcc46 > installed for ports building. I use ccache for both world and ports. In > /usr/local/etc/buildflags.conf I have set: > BUILDFLAGS_GCC= 4.6+ > GCC_DEFAULT_VERSION= 4.6+ > # USE_GCC= 4.6+ # breaks distcc > > Some ports builds unfortunately break under this setup because build is > looking for world's cc (gcc42 or clang). If I do this below, then the build > completes fine: > # setenv cc gcc46 && setenv cxx g++46 BUILDFLAGS_GCC takes effect if WITH_GCC is defined and the port being compiled does not set CC/CXX itself. For more information see buildflags.mk(1). -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?