https://gcc.gnu.org/bugzilla/show_bug.cgi?id=123976
--- Comment #105 from Sergey Fedorov <vital.had at gmail dot com> --- (In reply to Peter Dyballa from comment #52) > I thought of testing GCC16, but MacPorts wrote: > > The following dependencies will be installed: > gcc16-libcxx > libcxx-powerpc +emutls > python27-bootstrap > > So I threw away that thought. 1. MacPorts does not have gcc16, AFAIK. It also does not have libcxx for powerpc. You are probably referring to my port; of course, it assumes a coherent environment, i.e. the toolchain and ports provided by PPCPorts (and not upstream MacPorts). 2. That being said, `port -v install libgcc16 -stdlib_flag` (and likewise for gcc16) does away with pulling in libcxx-powerpc (gcc16-libcxx does not build anything but simply places headers where gcc finds them). 3. I do not guarantee that gcc16 builds on 10.5, since I did not test it, but it certainly does build on 32-bit powerpc on 10.6 (as well as 10.6 under Rosetta, but that needs specific variants of cctools and ld64). The compiler works fine. 4. If you prefer staying with official MacPorts, it is probably a better idea to use their ports. As long as / if those work.
