gcc error wrong ELF class ELFCLASS64

Question

I was trying to compile a program using an external compiled object coreset o   I wrote the public01 c test file and my functions are in computation c  both of which compiles   However its failing on linking it together   What might be the problem   gcc -o public01 x public01 o computation o coreset o ld  fatal  file coreset o  wrong ELF class  ELFCLASS64 ld  fatal  File processing errors  No output written to public01 x collect2  ld returned 1 exit status

User · Answer

You can specify  -m32  or  -m64  to select the compilation mode   When dealing with autoconf  configure  scripts  I usually set CC  gcc -m64   or CC  gcc -m32   in the environment so that everything is compiled with the correct bittiness   At least  usually   people find endless ways to make that not quite work  but my batting average is very high  way over 95   with it

User · Answer

You can specify  -m32  or  -m64  to select the compilation mode   When dealing with autoconf  configure  scripts  I usually set CC  gcc -m64   or CC  gcc -m32   in the environment so that everything is compiled with the correct bittiness   At least  usually   people find endless ways to make that not quite work  but my batting average is very high  way over 95   with it

User · Answer

sudo apt-get install ia32-libs

User · Answer

I think that coreset o was compiled for 64-bit  and you are linking it with a 32-bit computation o   You can try to recompile computation c with the  -m64  flag of gcc 1

User · Answer

It turns out the compiler version I was using did not match the compiled version done with the coreset o     One was 32bit the other was 64bit   I ll leave this up in case anyone else runs into a similar problem

User · Answer

It looks like the object file was compiled on a 64-bit toolchain  and you re using a 32-bit toolchain  Have you tried recompiling the object file in 32-bit mode

User · Answer

You can specify  -m32  or  -m64  to select the compilation mode   When dealing with autoconf  configure  scripts  I usually set CC  gcc -m64   or CC  gcc -m32   in the environment so that everything is compiled with the correct bittiness   At least  usually   people find endless ways to make that not quite work  but my batting average is very high  way over 95   with it

User · Answer

It turns out the compiler version I was using did not match the compiled version done with the coreset o     One was 32bit the other was 64bit   I ll leave this up in case anyone else runs into a similar problem

User · Answer

It turns out the compiler version I was using did not match the compiled version done with the coreset o     One was 32bit the other was 64bit   I ll leave this up in case anyone else runs into a similar problem

User · Answer

I think that coreset o was compiled for 64-bit  and you are linking it with a 32-bit computation o   You can try to recompile computation c with the  -m64  flag of gcc 1

User · Answer

You can specify  -m32  or  -m64  to select the compilation mode   When dealing with autoconf  configure  scripts  I usually set CC  gcc -m64   or CC  gcc -m32   in the environment so that everything is compiled with the correct bittiness   At least  usually   people find endless ways to make that not quite work  but my batting average is very high  way over 95   with it

User · Answer

It looks like the object file was compiled on a 64-bit toolchain  and you re using a 32-bit toolchain  Have you tried recompiling the object file in 32-bit mode

User · Answer

It turns out the compiler version I was using did not match the compiled version done with the coreset o     One was 32bit the other was 64bit   I ll leave this up in case anyone else runs into a similar problem

User · Answer

I think that coreset o was compiled for 64-bit  and you are linking it with a 32-bit computation o   You can try to recompile computation c with the  -m64  flag of gcc 1

User · Answer

I think that coreset o was compiled for 64-bit  and you are linking it with a 32-bit computation o   You can try to recompile computation c with the  -m64  flag of gcc 1

User · Answer

It looks like the object file was compiled on a 64-bit toolchain  and you re using a 32-bit toolchain  Have you tried recompiling the object file in 32-bit mode

User · Answer

sudo apt-get install ia32-libs

User · Answer

It looks like the object file was compiled on a 64-bit toolchain  and you re using a 32-bit toolchain  Have you tried recompiling the object file in 32-bit mode

[gcc] gcc error: wrong ELF class: ELFCLASS64

Examples related to gcc

Examples related to makefile