https://gcc.gnu.org/bugzilla/show_bug.cgi?id=123976
--- Comment #120 from Peter Dyballa <Peter_Dyballa at web dot de> ---
(In reply to Iain Sandoe from comment #119)
> additional:
>
> To bootstrap, i used a GCC-10.5 built using Apple gcc-4.2.1
It does not play a role which compiler is used to start building since in the
end it's GCC that builds its final stage. So I won't start building GCC-10. And
I am not sure which compiler was used to start building GCC-15.2, could be
GCC-7 I then had and used since MacPorts' default compiler for this job or port
had failed a few times.
Today a friend needs my physical help and I'll be off soon…
To repeat myself, another MacPorts user was the first one to report the build
problem (and its manual solution) to MacPorts. Later a third one asked for
being cc'd when something happens on the issue. So it's likely that I am not
the only one, maybe the only active one. (I invited the other two to try
building GCC-16 themselves and gave them the link to this site.)
You do not assume that a Makefile rule could be missing for darwin ppc32
("G4")? Which certainly is kind of rare and exceptional since Apple then
(towards the end of Leopard's/Mac OS X 10.6' lifetime) had faster PPC64 ("G5")
and also first intel based computers to offer.
I really would like to see Makefiles and the output of 'make -p' and 'make -d'
from Macs on which compilation happens without manual corrections. There must
be some differences, and at least one could cause the trouble on 32-bit PPC.
(Of course, the missing rule could be introduced or not added by some patch to
the build system…)
