https://gcc.gnu.org/bugzilla/show_bug.cgi?id=123976
--- Comment #203 from Sergey Fedorov <vital.had at gmail dot com> --- (In reply to Peter Dyballa from comment #197) > It is 10.5 from looking at the archive's name, or "powerpc-apple-darwin9-gcc > (GCC) 10.5.0" from identifying itself. Sergey show know exactly what it is. It is getting a bit hard to follow, and I do not know what exactly you are trying to do at the moment. Allow me to summarize what I suggested: 1. To build gcc11 or later, you need to use C++11-supporting compiler, this implies Xcode gcc does not suffice. gcc10 is the last gcc version that builds with Xcode gcc, for which reason it was chosen as an in-between step in MacPorts (gcc10-bootstrap port). 2. If you build outside of *ports, you do not need to use anything whatsoever from *ports, and better to use nothing from there (to make environment match what GCC upstream has tested). 3. You can build gcc10 "normally", without *ports involvement, and use it to build gcc16 outside of *ports. Why I suggested to use gcc10-bootstrap port is because it does not pull in other ports, so in principle should work just as good as any other gcc10 build. This is only a matter of saving some hours of compilation, so if it is not a concern or if it does not work and debugging takes longer, then rather avoid *ports altogether. 4. IF you use gcc10-bootstrap, there are ports for it in official MacPorts and in my PPCPorts fork: https://github.com/macports/macports-ports/blob/c2d1e785e2d99a10f41d3b55ebc61b729c90fd69/lang/gcc10-bootstrap/Portfile https://github.com/macos-powerpc/powerpc-ports/blob/7edfbb4502ab07dd6cfd849e5d33b6629ffe6c8c/lang/gcc10-bootstrap/Portfile >From what I can see, for 10.5 they are strictly identical. (For 10.6 there is a minor difference, but both should work on 10.6.8, whether native ppc or rosetta.) Either of these ports should build and work if built either for ppc only (`sudo port -v install gcc10-bootstrap -universal build_arch="ppc"`, to make it explicit and force the configuration) or, in case of 10.5, for ppc+ppc64, provided you run it on a G5 (this implies macports.conf has `universal_archs ppc ppc64` and build is `+universal`). I am not sure about other combos of archs, but probably ppc+i386 should work too. For the record, do not try universal builds on 10.6, those are broken (a known issue). 5. MacPorts does not provide pre-built ports for 10.5 (or any ppc/ppc64), which is why I pointed out at my pre-built package, which is for ppc+ppc64. It does work fine on 10.5.8 on G5 and, AFAIK, on a G4. But don't hold this against me, I have not tried ppc (32-bit) builds on 10.5 in ages myself. The safest option is always to build for the single arch, as long as you do not really need FAT build (on a G4 there is no reason to need FAT). 6. If you use SOME stuff from either MacPorts or PPCPorts but inside your custom builds, that may or may not work. Myself I can only say "for sure" (in a sense of "to the best of my knowledge", not in a sense of zero possible bugs) that my ports work in the primary supported environment when used as the complete, unaltered set-up.
