> 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
Not really sure what you are asking. legacy-support package is blind to
what ports might be using it. It just supplies functionality missing on
older OSes. If some hypothetical future wayland port needs these
functions, it presumably could use the PG in the same way as everything
else does.
Hi,
A quick question to the legacy-support devs: do you have any interest in
whether or not these support functions (plus whatever else is needed and
doable) could help building Wayland for Mac?
FWIW, I brought up the idea of running Wayland with Jeremy H. back when he was
still maintaining XQ
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
