clang-8.0 very strict -- can we think about changing the clang compiler list order?
Ken Cunningham
ken.cunningham.webuse at gmail.com
Sat Sep 28 10:20:46 UTC 2019
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 Jones <jonesc at hep.phy.cam.ac.uk> wrote:
>
>
>
>> On 27 Sep 2019, at 3:06 pm, Ken Cunningham <ken.cunningham.webuse at gmail.com> 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.
>>
>> What are the clang-using Linux distros defaulting, I wonder? That might tell us where they feel the codebase is presently...
>
> Our point of reference should be the Xcode clang versions. Most ports build fine on 10.14 using the system clang there, so what upstream version does this equate to , roughly ? My guess based on release times would be somewhere are clang 7.
>
> I am with Jeremy here, we need to start pushing away from clang 5.
>
> Chris
>
>>
>> Ken
>>
>
More information about the macports-dev
mailing list