Hello,

----------------------------------------------------------------------
/usr/bin/ld: warning: i386 architecture of input file
`../bin/linux_gnu/obj1.o' is incompatible with i386:x86-64 output

../bin/linux_gnu/obj1.o(.text+0x35): In function `s_Model':

: undefined reference to `_GLOBAL_OFFSET_TABLE_'

../bin/linux_gnu/obj.o(.text+0x663): In function `ls_getValue':

: undefined reference to `_GLOBAL_OFFSET_TABLE_'

../bin/linux_gnu/obj.o(.text+0x669): In function `ls_getValue':

: undefined reference to `globalObj'
---------------------------------------------------------------------

I tried build obj1.c code on AMD using gcc -m32 obj1.c. I got obj1.o file but when i tried to build shared object from obj1.o using LD, it displays some warning that is "incompatible with i386:x86-65 output".

I knew that i need to use -m elf_i386 LD flags to overcome this warning, but the same steps i followed on sparc64 ( i build obj1.c on sparc64 for 32 bit .o file then i used LD) LD does not display warning. How can i do the same on AMD, I do not understand why LD does not able to find the .o file is 32 bit. Are there any way to not to specifiy -m elf_i386 to generate .o file to shared object?

Please let me know your suggestions.

Thanks,
Dayalan

It all depends on the compiler/linker specifications when they're configured. Are you saying that the sparc64 took -m32 with gcc and didn't require it of ld? When you get down into specific processors you can't expect two procedures to behave the same on two different architectures.

You might be able to link using gcc with the same -m option instead of using ld.
ta0kira

Sparc64 does not need -m32 we need to include -xarch=v9 then compiler will build 64 bit ELF, but ld on Sparc64 is able to understand whether the ELF is 32 bit or 64 bit, but it is not happening in Linux.

Yes you are correct, i will be able to gcc to link object files using -m option.

Thank you for your reply.

Thanks,
Dayalan