Date: Sat, 22 Feb 2014 22:50:01 GMT From: Gerald Pfeifer <gerald@pfeifer.com> To: freebsd-ports-bugs@FreeBSD.org Subject: Re: ports/178557: Ports with USE_GCC=any don't respect local CC and CXX settings Message-ID: <201402222250.s1MMo19f085928@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/178557; it has been noted by GNATS. From: Gerald Pfeifer <gerald@pfeifer.com> To: bug-followup@FreeBSD.org Cc: Subject: Re: ports/178557: Ports with USE_GCC=any don't respect local CC and CXX settings Date: Sat, 22 Feb 2014 23:42:18 +0100 (CET) On Mon, 13 May 2013, Mikhail T. wrote: >>Description: > Even though I set CC and CXX in make.conf to gcc48 and g++48 > respectively, ports such as audio/nas or graphics/devil, which > specify USE_GCC=any, attempt to build using the regular gcc > instead. The way I understand things, /etc/make.conf is for setting system wide defaults. USE_GCC or USES=compiler, on the other hand, are specific per port settings that override system wide defaults. If the ports infrastructure would now honor setting of CC and CXX at the global level (/etc/make.conf), how could special requirements to build a certain port be made? In fact, if USE_GCC=any, and CC is set manually, should the ports infrastructure really check (and how) whether CC points to GCC as opposed to some other compiler and then, and only then, use it? If you prefer a certain version of GCC, what you can do is set GCC_DEFAULT_VERSION on Mk/bsd.gcc.mk, and I am shortly going to commit a patch to move a variation of that to Mk/bsd.default-versions.mk. That should help in a case like that, since USE_GCC=any will then use that version. Grald
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201402222250.s1MMo19f085928>