Kai Ruottu wrote:
If you still aim to produce apps for the old installed Linux, you should produce your crosstoolchain to target to that system, not for "something else" which is more up-to-date and with newer components. So producing gcc-3.4.3 is fully OK but replacing the existing C library in the crosstoolchain is totally wrong !
It is really wacky that I think to elaborate this but when the world has gone upside down nowadays, some old facts about GCC-building could be repeated: o the C library doesn't belong to GCC, it is something which already exists or at least is assumed to exist o building the C library is a totally separate process and it has nothing to do with the GCC build o building only binutils and GCC is the normal way to produce a cross-GCC. GCC will be built with the existing target C library and the target binutils being preinstalled before the GCC build starts If people now more don't know how to build GCCs, something about the old "silent know-how" has seemingly disappeared...
