svn commit: r388648 - in head/net: asterisk11 asterisk13

[Guido Falsi]

On 11/08/15 20:01, Gerald Pfeifer wrote:
> On Fri, 5 Jun 2015, Guido Falsi wrote:
>> Author: madpilot
>> Date: Fri Jun  5 23:30:10 2015
>> New Revision: 388648
>> URL: https://svnweb.freebsd.org/changeset/ports/388648
>>
>> Log:
>>   - Update asterisk11 to 11.18.0
>>   - Update asterisk13 to 13.4.0
>>   - Add experimental option to allow using base compiler instead of
>>     ports gcc (mainly meant to allow compiling with clang)
> 
> Note, it's GCC these days (and I just checked, the other cases
> in the ports tree use this spelling), so I went ahead and made
> this change to these two ports.

I have no objection with your change, I waa unsure what spelling to use
when I added that option.

> 
> Perhaps we can abstract this into a global GCC_DESC at one point?
> 

As someone already expressed it's not easy.

Asterisk uses it to mean the pretty standard "Use GCC to compile this,
even if clang is available".

Problem is sometimes GCC is used to mean "any GCC, GCC from base is ok"
some other times it means "I want a modern GCC, GCC from base isn't good
enough". Descriptions aren't always making this really clear also.

In recent releases asterisk can be compiled with clang, but I have
observed it core dump sometimes when compiled with clang, while working
flawlessly with gcc so I left the default there.

IMHO usually the GCC option should be meant to be used when one wants
GCC from ports, while using a base compiler should should be a default
or the alternative.

-- 
Guido Falsi <madpilot at FreeBSD.org>