https://gcc.gnu.org/bugzilla/show_bug.cgi?id=123976
--- Comment #48 from Sergey Fedorov <vital.had at gmail dot com> --- (In reply to Peter Dyballa from comment #47) > I promised to try a *clean build* with MacPorts, afterwards, next week, and > after this a combination of clean build until MacPorts tries to extract GCC > 16 to have the prerequisites activated in MacPorts and then performing the > actual build outside of MacPorts, in July. I think it is really better to keep issues distinct at this point, to minimize the burden on gcc upstream. 1. As Iain noted, in order for this problem to be addressed here in upstream, it must be shown to exist without MacPorts/PPCPorts/Homebrew or any other external build system involvement. (I understand that it takes time, effort and cpu cycles, but without that it is not clear how to reproduce it.) 2. If the failure reproducibly happens in official MacPorts installation, with gcc-15 port, on 10.5.8, it can (and perhaps should) be raised to MacPorts (on Trac). 3. If the failure reproducibly happens in my ppcports installation with my gcc-16 port, feel free to open an issue here: https://github.com/macos-powerpc/powerpc-ports/issues Anything specific to MacPorts or its forks cannot be addressed here, since nobody will install a separate build environment just to debug this. > gcc10-bootstrap is only listed as a build dependency here, but in reality it > does not exist on my Leopard, because it does not build here. This is an issue to discuss with MacPorts, if you use official MacPorts, or with me, if you use my fork. To the best of my knowledge, gcc10-bootstrap builds fine on 10.5 and 10.6, with the reservation that on 10.6 the build cannot be universal (it is already handled in the port correctly). Proof: https://macos-powerpc.org/packages/gcc10-bootstrap (for 10.6) https://macos-powerpc.org/packages_ppc64/gcc10-bootstrap (for 10.5)
