Fwd: gcc 4.2.0 compilation failing on x86_64 machine

[Kai Ruottu]

Kai Ruottu wrote:
> The produced GCC is "brain damaged", some day someone maybe wants to 
> try the '-m32' option and
> then it gives weird errors again!
I forgot to add that in this situation it is too late to add all the 
32-bit development parts for THIS GCC, only
parts for the original GCC will be added just as the missing glibc 
parts!  During the GCC build the 32-bit
'libgcc', 'libiberty', 'libstdc++' etc. should be produced in order to 
get that support for 32-bit apps production.

It really doesn't matter if the produced GCC is brain damaged if the 
users know it being that and then don't
try anything which it "should do" but was not wanted to do that!