Re: gcc and g++ version setting in buildflags.conf
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? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: gcc and g++ version setting in buildflags.conf
> however Dominic haven't replied Bummer. Hope he will be reachable soon. > I've never got hang of deploying ccache ... it discouraged me in term of > debugging potential problems. You can always disable it & re-enable it. Saves compile time for sure. Usually I have to re-start builds because ccache bombs maybe 50% of the time - still wort it. Buildflags.conf is definitely needed if you use ccache for ports because it allows to specify NOCCACHE for each port that cannot use it (mostly cmake incompatibility with ccache) Regards. -- View this message in context: http://freebsd.1045724.n5.nabble.com/gcc-and-g-version-setting-in-buildflags-conf-tp5769675p5770410.html Sent from the freebsd-ports mailing list archive at Nabble.com. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: gcc and g++ version setting in buildflags.conf
Speaking of bsdadminscripts I have problem with
pkg_validate, however Dominic haven't replied, so he
may be busy.
I've never got hang of deploying ccache, sorry. Usually
just heard something in the line "make sure you don't
use ccache/clean properly before rebuild" so it discouraged
me in term of debugging potential problems.
I set per port flags by simple means of:
.if ${.CURDIR:M*/directory/directory}
AAA=
.endif
My setup predates bsdadminscripts and
USE_GCC=4.6+ I think, so maybe it's not
flavour of the month, but it usually works,
more or less.
Unless something really hangs on trying
/usr/bin/cc, which is clang here too, yes.
But it should not, as porters handbook
is concerned, and x11 parts which were
hardcoded around trying it are already fixed.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/gcc-and-g-version-setting-in-buildflags-conf-tp5769675p5770364.html
Sent from the freebsd-ports mailing list archive at Nabble.com.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
gcc and g++ version setting in buildflags.conf
Hi Jakub,
I forgot to mention I have ccache enabled for port builds. No matter, I
could place this in make.conf:
CC:=${CC:C,^gcc46,/usr/local/libexec/ccache/world/gcc46,1}
And it would work. What I don't understand is that when I was building
security/gnupg1 the port kept calling "cc" (clang compiler in world) instead
of gcc46. As I stated, only when I did "# setenv cc gcc46 " is when build
started using gcc46. Output from the build process shows:
/usr/local/bin/ccache cc -DHAVE_CONFIG_H . (etc)
cc: warning: argument unused during compilation: '-I .'
cc: warning: argument unused during compilation: '-I ..'
clang is not hard-coded in tyhe Makefile as:
CFLAGS:=${CFLAGS:S/-pipe//g}
.if ${CC} == "clang"
CFLAGS:=${CFLAGS:S/$/ -std=c89/}
.endif
I use buildflags.conf because I find it is easier to maintain per-port
preferences.
These don't work either, BTW so I think I might advise the port maintainer
for bsdadminscripts.
BUILDFLAGS_GCC_CC= /usr/local/libexec/ccache/world/gcc46
BUILDFLAGS_GCC_CXX= /usr/local/libexec/ccache/world/g++46
BUILDFLAGS_GCC_CPP= /usr/local/libexec/ccache/world/cpp46
BUILDFLAGS_GCC_CC= 4.6+
BUILDFLAGS_GCC_CXX= 4.6+
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/gcc-and-g-version-setting-in-buildflags-conf-tp5769675p5770358.html
Sent from the freebsd-ports mailing list archive at Nabble.com.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: gcc and g++ version setting in buildflags.conf
I just use CPUTYPE?=native CC=gcc47 CXX=g++47 CPP=cpp47 If port does not intentionally choose clang (mplayer, libreoffice) it works. -- View this message in context: http://freebsd.1045724.n5.nabble.com/gcc-and-g-version-setting-in-buildflags-conf-tp5769675p5770354.html Sent from the freebsd-ports mailing list archive at Nabble.com. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
gcc and g++ version setting in buildflags.conf
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 Any suggestions are welcome! -- View this message in context: http://freebsd.1045724.n5.nabble.com/gcc-and-g-version-setting-in-buildflags-conf-tp5769675.html Sent from the freebsd-ports mailing list archive at Nabble.com. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
