compiling 32 bit code under amd64

Marvin Dickens mpdickens at tlanta.com
Wed Dec 8 05:03:24 UTC 2004


On Tue, 2004-12-07 at 22:28 -0600, Aleksander Demko wrote:

> [testuser at moya tmp]$ gcc -m32 `pkg-config --cflags --libs glib-2.0`
> 1.c
> /usr/bin/ld: skipping incompatible /usr/lib64/libglib-2.0.so when
> searching for -lglib-2.0
> /usr/bin/ld: skipping incompatible /usr/lib64/libglib-2.0.a when
> searching for -lglib-2.0
> [testuser at moya tmp]$ file /usr/lib/libglib-2.0.so.0*
> /usr/lib/libglib-2.0.so.0:       symbolic link to
> `libglib-2.0.so.0.400.8'
> /usr/lib/libglib-2.0.so.0.400.7: ELF 32-bit LSB shared object,
> Intel 80386, version 1 (SYSV), stripped
> /usr/lib/libglib-2.0.so.0.400.8: ELF 32-bit LSB shared object,
> Intel 80386, version 1 (SYSV), stripped
> 
> 64-bit is fine:
> [testuser at moya tmp]$ gcc -m64 `pkg-config --cflags --libs glib-2.0`
> 1.c
> [testuser at moya tmp]$
> 
> 
> Any ideas?

Hello Aleksander, 

This smells like an automake/ToCIdentifier thing. 
The name of your file is "1.c" and consists of a
single digit and is being replaced with an underscore by ToCIdentifier.
In turn, automake fails.


Best regards

Marvin Dickens




More information about the fedora-list mailing list