Linking of object files from different compilers for ARM

Linking of object files from different compilers for ARM

[Yaroslav Karulin]

   Hello!

   I have two files: foo.c and main.c. foo.c is compiled with RVTC 2.2 
compiler. main.c is compiled with gcc compiler (configured with 
--target=arm-elf). I cannot link them together using gcc linker.
   But it's possible to link files if I use CodeSourcery version of gcc.
CodeSourcery guys writes that they have added full EABI support and hope 
to submit it to the gcc 4.1.
   So, the question is what's the difference between CodeSourcery's 
version of gcc and FSF version? And is EABI support really submitted to 
the gcc 4.1?
-- 
Yaroslav

Re: Linking of object files from different compilers for ARM

[Daniel Jacobowitz]

On Fri, Oct 14, 2005 at 09:49:42AM +0300, Yaroslav Karulin wrote:
>   Hello!
> 
>   I have two files: foo.c and main.c. foo.c is compiled with RVTC 2.2 
> compiler. main.c is compiled with gcc compiler (configured with 
> --target=arm-elf). I cannot link them together using gcc linker.
>   But it's possible to link files if I use CodeSourcery version of gcc.
> CodeSourcery guys writes that they have added full EABI support and hope 
> to submit it to the gcc 4.1.
>   So, the question is what's the difference between CodeSourcery's 
> version of gcc and FSF version? And is EABI support really submitted to 
> the gcc 4.1?

The difference is that it's configured for an EABI target, not an ELF
(legacy) target.  Build an arm-none-eabi compiler instead of an arm-elf
compiler and it should work.

-- 
Daniel Jacobowitz
CodeSourcery, LLC

Re: Linking of object files from different compilers for ARM

[Paul Brook]

On Friday 14 October 2005 07:49, Yaroslav Karulin wrote:
>    Hello!
>
>    I have two files: foo.c and main.c. foo.c is compiled with RVTC 2.2
> compiler. main.c is compiled with gcc compiler (configured with
> --target=arm-elf). I cannot link them together using gcc linker.
>    But it's possible to link files if I use CodeSourcery version of gcc.
> CodeSourcery guys writes that they have added full EABI support and hope
> to submit it to the gcc 4.1.
>    So, the question is what's the difference between CodeSourcery's
> version of gcc and FSF version? And is EABI support really submitted to
> the gcc 4.1?

The CodeSourcery releases are made off csl-arm-branch in CVS.

I think all the EABI changes are now in 4.1.
You need to configure for the arm-eabi target, not arm-elf.

Note that theres no such thing as the "gcc linker". You probably mean GNU 
binutils/ld.

Paul