Infinate loop in gcc 3.4.5 make-gcc
Re:Infinate loop in gcc 3.4.5 make-gcc
Glad to hear it wasn't my stuff that borked. But I agree with Candy - you should bring this up with the maintainers of autoconf.
Every good solution is obvious once you've found it.
-
srg
Re:Infinate loop in gcc 3.4.5 make-gcc
I see, it happends when I go make all, or make all-gcc, rather than ./configure, would this make a difference?Solar wrote: Glad to hear it wasn't my stuff that borked. But I agree with Candy - you should bring this up with the maintainers of autoconf.
Re:Infinate loop in gcc 3.4.5 make-gcc
No idea, really. You could try to find out (surgeon approach), or complain with the autoconf, make and gcc team (shotgun approach)... 
Every good solution is obvious once you've found it.
-
srg
Re:Infinate loop in gcc 3.4.5 make-gcc
The "Here, shoot me down on flames" approach LOLSolar wrote: No idea, really. You could try to find out (surgeon approach), or complain with the autoconf, make and gcc team (shotgun approach)...
Re:Infinate loop in gcc 3.4.5 make-gcc
Seeing the output and the fact that both make and gcc already report and complain about files-from-the-future correctly, I guess it's autoconf. Complain to them and tell them to complain to the gcc/make team if it isn't their problem.
Guess this would be the Oliver-Twist approach (please sir, I'd like a bugfix more).
Guess this would be the Oliver-Twist approach (please sir, I'd like a bugfix more).
-
srg
Re:Infinate loop in gcc 3.4.5 make-gcc
I've also fixed the m68k-elf problem by using binutils 2.15 rather than 2.16/.1. The rest use 2.16.1.