Apple does a lot in it's clang fork to relax the restrictiveness.
Seriously, set your default compilers to what 10.6.8 has to live with; at least
share in it with us!
But I can see I'm outvoted here. My great dream of no older systems tickets
dies.
:)
K
> On Sep 28, 2019, at 01:14, Chris J
> On 27 Sep 2019, at 3:06 pm, Ken Cunningham
> wrote:
>
> I think it would be fair to invite everyone to try setting the default
> compiler list for a week on your own systems to our current macports clang
> progression!
>
> Compilers are always ahead of the codebase by a couple of years.
> On Sep 26, 2019, at 21:46, Ken Cunningham
> wrote:
>
>> FYI clang-8.0, new default on 10.6.8, is very strict
>>
>> appears will have to add to blacklist on many ports
>
>
> So as much as I would have put clang-5.0 first as the default compiler if the
> system clang won't work, I underst
I think it would be fair to invite everyone to try setting the default compiler
list for a week on your own systems to our current macports clang progression!
Compilers are always ahead of the codebase by a couple of years.
What are the clang-using Linux distros defaulting, I wonder? That might
Hi,
I would not be particularly in favour of changing things as you suggest.
For me the defaults as they are are correct. They should start with the
newest clang available and work back, in order.
For specific ports that have issues, either fix the port to work with a
recent clang, or if not
> FYI clang-8.0, new default on 10.6.8, is very strict
>
> appears will have to add to blacklist on many ports
So as much as I would have put clang-5.0 first as the default compiler if the
system clang won't work, I understand that as some payback for all this older
systems support effort, it'
