> So other distro's did it too. Why did nobody complain till RedHat > did it? Because no one else decided to use, as the default, a bleeding edge > compiler that not only won't compile the kernel but won't even touch a lot of > userspace code either. Actually the first people to do exactly that were Debian, who shipped a compiler that couldnt reliably build a kernel for the time period. Thats one of the reasons they put in gcc272. Its good sense to tie large critical pieces of hard to validate code to the compiler. There is a reason you'll find any good software company maintains old releases in archives with the build environment to reproduce them exactly Alan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
- Re: non-gcc linux? (was Re: Wh... Ralf Baechle
- Re: non-gcc linux? (was Re: Where ... Andi Kleen
- Re: non-gcc linux? (was Re: Wh... Christoph Hellwig
- Re: non-gcc linux? (was Re: Wh... Kai Henningsen
- Re: non-gcc linux? (was Re: Wh... Michael Meissner
- Re: non-gcc linux? (was Re: Wh... Kai Henningsen
- Re: non-gcc linux? (was Re: Where ... Thomas Pornin
- Re: non-gcc linux? (was Re: Where ... Kai Henningsen
- Re: Where did kgcc go in 2.4.0-test10 ? Tom Rini
- Re: Where did kgcc go in 2.4.0-test10 ? Alan Cox
- Re: Where did kgcc go in 2.4.0-test10 ? Alan Cox
- Re: Where did kgcc go in 2.4.0-test10 ? Mike Galbraith
- Re: Where did kgcc go in 2.4.0-test10 ? Jeff Garzik
- Re: Where did kgcc go in 2.4.0-test10 ? Wayne . Brown
- Re: Where did kgcc go in 2.4.0-test10 ? Jeff Garzik
- Re: Where did kgcc go in 2.4.0-test10 ? J . A . Magallon
- Re: Where did kgcc go in 2.4.0-test10 ? Wayne . Brown