Kai Ruottu writes:
> Paulo J. Matos wrote:
> > Probably this is due to the fact that in Gentoo intel core duo follow
> > the amd64 branch, since they are 64 bit processors...
> >
> > checking whether the C compiler works... configure: error: cannot run
> > C compiled programs.
> > /home/pmatos/gcc411-build/./gcc/xgcc
> > -B/home/pmatos/gcc411-build/./gcc/ -B
> > /home/pmatos/gcc-bin/x86_64-unknown-linux-gnu/bin/
> > -B/home/pmatos/gcc-bin/x86_64-unknown-linux-gnu/lib/ -isystem
> > /home/pmatos/gcc-bin/x86_64-unknown-linux-gnu/include -isystem /hom
> > e/pmatos/gcc-bin/x86_64-unknown-linux-gnu/sys-include -m32 -o
> > conftest -O2 -g -O2 conftest.c >&5
> > /usr/bin/ld: skipping incompatible /usr/lib/../lib/libc.so when
> > searching for -lc
> > /usr/bin/ld: skipping incompatible /usr/lib/../lib/libc.a when
> > searching for -lc
> > /usr/bin/ld: warning: i386:x86-64 architecture of input file
> > `/usr/lib/../lib/crt1.o' is incompatible with i386 output
> With '-m32' the 32-bit libraries in '/usr/lib' will be used ! The
> '/usr/lib64' has
> the 64-bit x86_64 libraries!
>
> Maybe your Gentoo is a "custom" Linux with unstandard conventions?
>
> The Ubuntu Linux/x86_64 is this kind of "custom" Linux where the
> 64-bit libs are in '*lib' and the 32-bit libs in '*lib32'. The
> Fedora, SuSE etc. then use the convention which the GCC sources
> assume a Linux/x86_64, or any other 64-bit Linux using
> ('mips64-linux-gnu', 'ppc64-linux-gnu', 'sparc64-linux-gnu',.....)
Oh. My. God. That is so truly screwed I don't know where to begin.
No wonder gcc was confused!
Andrew.
