Re: removal of cxx11 PG and pre-snowleopard systems having some issues

I saw the same in a dozen or so ports. It seems, at first glance, that when *gcc-3.* and *gcc-4.* are blacklisted, the fallback on PowerPC does not go to gcc-6 or gcc-7, but through to the clang chain. compiler.fallback-prepend macports-gcc-6 macports-gcc-7 in the Portfiles seems to fix it

Re: removal of cxx11 PG and pre-snowleopard systems having some issues

> Can you give specific examples, preferably with logs? On ppc, > macports-gcc compilers are preferred over macports-clang: > > > So I don't immediately see how what you describe could happen, unless > the

Re: removal of cxx11 PG and pre-snowleopard systems having some issues

On 2019-10-7 07:27 , Ken Cunningham wrote: > To no great surprise, as I didn’t bother to try it before now, the move from > the cxx11 PG to the new compiler spec system seems to be having some issues > on my older systems. MacPorts is calling in libomp and clang on PPC, which of > course are

removal of cxx11 PG and pre-snowleopard systems having some issues

To no great surprise, as I didn’t bother to try it before now, the move from the cxx11 PG to the new compiler spec system seems to be having some issues on my older systems. MacPorts is calling in libomp and clang on PPC, which of course are not (presently at least) available. So you may see