https://gcc.gnu.org/bugzilla/show_bug.cgi?id=123976
--- Comment #230 from Peter Dyballa <Peter_Dyballa at web dot de> --- (In reply to Iain Sandoe from comment #228) > (In reply to Peter Dyballa from comment #227) > > > Iain, you do understand that make and Makefile have the necessary knowledge > > and can create the missing symlinks, they just don't "feel" a need to do so? > > Remarks like this, and comment #220 are not appropriate or helpful and get > us no nearer to resolving the issue. OK, a computer or some programme has not feelings, but you do share the insight that Makefile has all theoretical knowledge except the one rule that makes it necessary to create the missing three symlinks at a particular moment? (And why are three other symlinks created from the same rule or rules set?) > > You were asked in comment #26 - to reduce the scope of the problem to > something that would stand reasonable chance of analysis - that is standard > procedure, nothing special to powerpc-darwin. You did not give any advice how to do that. Me, I do not see a great difference whether MacPorts is used, whether it's "clean", or whether only a bit of it needs to be used. If the software and its build system are not robust enough they should return into a garage. Evolution is certainly a pretty good idea providing fit for instant use things. (A market is a system of corruption.) > > Yet we are at comment #227 and only just getting to that point. I already was at that point when I reported the issue, when I asked the GNU Make support for help… (could be GNU Make has a PPC bug) > > This is taking time away from other macOS support, and we need to focus on > getting a solution > > The branch works under "standard" conditions - as demonstrated by the test > results here: I would not describe Rosetta as close to some "standard" conditions, but it's my opinion and I never had to try Rosetta (maybe I used it inherently when I created and tested diversely fat binaries). > https://github.com/user-attachments/files/29629215/summ-powerpc-darwin9-gcc- > 16-1-darwin-8931-rosetta.txt there is no reason for keeping this BZ open > unless we are making some actual progress. I have no idea of what you actually intend, what your plan or road map is, and therefore rely as a computer on exact input. When I have to think over you propositions I can easily make mistakes because my background is system administration. I could have started weeks (?) ago comparing Makefiles and the output of 'make -p' and even 'make -d' while my PowerBook was gently compiling this or that. OK, I'll download your *rosetta.txt and try to compare what GNU Emacs saved as last build log!
