|
Failure of gcc -m32 on an x86_64
gcc -m32 fails with the message:
"/usr/bin/ld: crt1.o: No such file: No such file or directory
collect2: ld returned 1 exit status"
The package glibc-devel-2.3.3-27 installs the file /usr/lib64/crt1.o, should it also be installing the file /usr/lib/crt1.o, etc, so that gcc -m32 will work?
I have tried fixing this by installing similar 32-bit packages (sorry, don't have the name of the package) but rpm complained of conflicts.
This can be a real hassle as configure files sometimes test gcc by using the -m32. One
example is GNU GRUB v0.94 where the configure script failed. I also have some 32-bit applications that I would like to compile for my x86_64 system, but sometimes that fails
if I use gcc without -m32 because you get seg faults if they treat pointers as 4 byte.
Does anyone know a way of fixing this problem? I've read about this elsewhere but haven't found an answer.
SPECS:
CPU: 2 x 3.2GHz Xeon Nocona
Linux: 2.6.5-1.358smp
Distro: FC2 x86_64
gcc: 3.3.3 20040412 (Red Hat Linux 3.3.3-7)
|
