Date: Wed, 19 Dec 2012 01:18:20 +0100 From: Dominic Fandrey <kamikaze@bsdforen.de> To: Beeblebrox <zaphod@berentweb.com> Cc: freebsd-ports@freebsd.org Subject: Re: gcc and g++ version setting in buildflags.conf Message-ID: <50D107CC.4050903@bsdforen.de> In-Reply-To: <1355642781949-5769675.post@n5.nabble.com> References: <1355642781949-5769675.post@n5.nabble.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50D107CC.4050903>