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 *manually* of course, although that clearly is NO SOLUTION obviously. My Leopard PPC system is just about done rebuilding — I manually forced the broken ports to gcc-6 — and then will see if I can help figure out where the blacklisting is falling through. K > On Oct 6, 2019, at 7:28 PM, Joshua Root <j...@macports.org> wrote: > > On 2019-10-7 12:58 , Ken Cunningham wrote: >>> Can you give specific examples, preferably with logs? On ppc, >>> macports-gcc compilers are preferred over macports-clang: >>> <https://github.com/macports/macports-base/blob/v2.6.1/src/port1.0/portconfigure.tcl#L1097> >>> >>> So I don't immediately see how what you describe could happen, unless >>> the ports are also blacklisting *gcc* or something. >> >> >> Here it begins : <https://trac.macports.org/ticket/59195> >> >> I will try to see if I can sort out where things are going wrong. > > OK, that's certainly not expected behaviour, but it's nothing to do with > cxx11. > > - Josh