Date: Tue, 18 Dec 2012 03:13:06 -0800 (PST) From: Jakub Lach <jakub_lach@mailplus.pl> To: freebsd-ports@freebsd.org Subject: Re: gcc and g++ version setting in buildflags.conf Message-ID: <1355829186764-5770364.post@n5.nabble.com> In-Reply-To: <1355828028468-5770358.post@n5.nabble.com> References: <1355642781949-5769675.post@n5.nabble.com> <1355825026067-5770354.post@n5.nabble.com> <1355828028468-5770358.post@n5.nabble.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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}
AAAAAAA=
.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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1355829186764-5770364.post>