Date: Fri, 12 Oct 2012 09:54:01 +0200 From: Claude Buisson <clbuisson@orange.fr> To: matt <sendtomatt@gmail.com> Cc: Mark Linimon <linimon@lonesome.com>, freebsd-current@FreeBSD.org, freebsd-ports@freebsd.org Subject: Re: [HEADSUP] FYI: patch to ports that do not build with clang has been committed Message-ID: <5077CC99.4010104@orange.fr> In-Reply-To: <507787CF.1090705@gmail.com> References: <20121010004523.GA15209@lonesome.com> <5075365C.4050400@orange.fr> <507787CF.1090705@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/12/2012 05:00, matt wrote:
>
>>>
>>> I have made changes to ports/Mk/bsd.gcc.mk that allow the addition of
>>> "USE_GCC=any" to a port's Makefile, and then committed that change to
>>> various ports. In most (but not all!) cases this will tell the port
>>> "build with gcc instead of clang" (*) .
>>>
>>
>> Why not USE_GCC ?= any for the poor guys like me who build (some)
>> ports with
>> USE_GCC=4.6 ?
>>
>>> For those users with CC installed as gcc (including -stable), this
>>> patch should have no effect. Variations of combinations have been
>>> heavily tested on pointyhat-west. If there are any regressions, please
>>> contact me.
>>>
>>
>>
>
> Does this override setting CC explicitly in make.conf?
> Sorry if it's a dumb question, not sure exactly the hierarchy of USE_GCC
> vs CC in the make system.
>
Dumb as I am, I also wonder when I see that in multimedia/x264:
...
USE_GCC= any
...
.if ${PORT_OPTIONS:MGCC44}
USE_GCC?= 4.4+
.endif
...
which seems to deny the intent of the GCC44 option
Sorry but I can not make the test at this present time
> Matt
Claude Buisson
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5077CC99.4010104>