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

[John Marino]

On 11/9/2015 3:11 PM, Guido Falsi wrote:
> On 11/09/15 14:00, Alexey Dokuchaev wrote:
>> On Mon, Nov 09, 2015 at 01:45:37PM +0100, Gerald Pfeifer wrote:
>>> On Mon, 9 Nov 2015, John Marino wrote:
>>>> "current GCC" is a bit confusing to me.  Do you mean "Ports GCC"?  
>>>> Or "appropriate GCC" ?  I think the wording would confuse users too.
>>
>> +1; "current GCC" is a bit vague; certainly seasoned ports hackers would
>> know what it means, but for user Joe it might not be immediately clear
>> when this message pops up in dialog(1) without ^C'ing and reading the
>> Makefile.
>>
>>> I guess the full version would be "Use GCC, just not the crappy old
>>> version in base of older versions of FreeBSD" (except for lang/gambit-c
>>> and cad/ghdl).
>>>
>>> Perhaps
>>>
>>>   GCC_DESC?=	Use GCC (from ports)
>>
>> I'd vote for "Use modern GCC (from ports)" or "Build with modern GCC".
>>
> 
> I agree with the idea, really.
> 
> I just feel compelled to point out one detail, the GCC option could also
> used to indicate the port should compile using any GCC, also including
> the one included in base. Usually this does not happen just because
> depending on ports GCC exclusively is easier than allowing base one too.
> 
> I agree this is really a minor issue.
> 

But that's pie-in-the-sky.
If it works with base gcc, there wouldn't be a GCC options.
If the default GCC is 4.8 (soon to be 4.9) then there's a good chance
gcc 4.7 or 4.6 won't build.

Lastly, you can use make.conf to force a higher GCC than 4.8 but that's
a global option.

John