>> > These are *ancient*, the last version 10.11.6 was released in
>> > 2018. Even if we find one, I think we must not introduce any
>> > workaround for such outdated systems.
>>
>> *Must not*? This is a bit harsh IMHO.
>
> Any workaround we introduce will have to be removed at some point.
I thought of a cast or something similar, which I wouldn't call a
'workaround', and which could stay.
>> The problem could also be in the used clang versions, which are
>> probably used on non-macOS platforms, too.
>
> ... which is also 5 years old, so the same rationale applies.
I really don't understand why the idea of potentially fixing the
problem gets rejected without even looking whether something simple
exists.
Werner
