From: MNShukla <mnshukla@cirrus.stpp.soft.net>
To: Nick Clifton <nickc@cambridge.redhat.com>
Cc: gcc <gcc@gcc.gnu.org>
Subject: Re: Query...
Date: Thu, 19 Apr 2001 21:54:00 -0000 [thread overview]
Message-ID: <3ADFC019.451A85D5@cirrus.stpp.soft.net> (raw)
In-Reply-To: <m3d7a9ypbk.fsf@north-pole.nickc.cambridge.redhat.com>
Hi Nick,
Nick Clifton wrote:
> Hi Shukla,
>
> > I am generating obj files by using ARM-gcc, gcc-for-PC(intel) and
> > ARM-ADS. I am getting difference in the ELF-header, the values of
> > EI_PAD of e_ident[] is as follows--
> >
> > EI_PAD = 0x61 for ARM-gcc and
> > EI_PAD = 0x00 for ARM-ADS and PC-gcc.
> >
> > Can somebody point me what does it signify?
>
> You are looking at an old version of the ELF spec. That field
> (e_ident[7]) is now called EI_OSABI, and the EI_PAD field is now two
> bytes further on.
>
> The EI_OSABI field is used to distinguish binaries for the same
> architecture but which target different Operating Systems and/or
> different Application Binary Interfaces. A value of 0 means "default"
> or "uninitialised". A value of 0x61 (or 97 in decimal) is defined in
> the spec as:
>
> #define ELFOSABI_ARM 97 /* ARM */
>
> In the case of GCC this field is being used to distinguish between
> binaries built by old versions of gcc (which set the field to 0)
> and new(er) versions of gcc. The older versions did not implement the
> ARM ELF ABI correctly, and so the linker has to work around this
> problem, provided that it can detect the old binaries.
>
Can OBJ's, created by older ELF spec., be linked with GCC-linker which
uses newer ELF spec.?
Actually, I want to create OBJ's by using ARM-ADS(v1.1) and link it with
arm-linux-gcc.
>
> > Now, if I want to link obj's generated by ARM-ADS with obj generated
> > by ARM-gcc, it is not able to link and says format different.
>
> What, precisely, is the error message that you are receiving ?
>
The error messages areas---
-------/bin/ld : Error : strlen.o compiled for EABI version 0, whereas
MN1.out is compiled for version 2.
File format not recognized : failed to merge target specific data of file
............./lin/libc.a (strlen.o)
-------/bin/ld : Error : write.o compiled for EABI version 0, whereas
MN1.out is compiled for version 2.
File format not recognized : failed to merge target specific data of file
............./lin/libc.a (write.o)
-------/bin/ld : Error : fflush.o compiled for EABI version 0, whereas
MN1.out is compiled for version 2.
File format not recognized : failed to merge target specific data of file
............./lin/libc.a (fflush.o)
-------/bin/ld : Error : freer.o compiled for EABI version 0, whereas
MN1.out is compiled for version 2.
File format not recognized : failed to merge target specific data of file
............./lin/libc.a (freer.o)
-------/bin/ld : Error : lseeker.o compiled for EABI version 0, whereas
MN1.out is compiled for version 2.
File format not recognized : failed to merge target specific data of file
............./lin/libc.a (lseeker.o)
---------------
---------------
---------------
With Best Regards,
Shukla
(Mahesh Narain Shukla)
next prev parent reply other threads:[~2001-04-19 21:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-19 3:29 Query MNShukla
2001-04-19 5:51 ` Query Nick Clifton
2001-04-19 21:54 ` MNShukla [this message]
2001-04-20 3:29 ` Query Philip Blundell
2001-04-19 9:47 ` Query Toshi Morita
-- strict thread matches above, loose matches on Subject: below --
2003-04-24 11:48 Query Vijay Kamath
2003-04-24 12:25 ` Query Andrew Haley
2002-03-01 21:14 query sunil suhas petwe
2002-03-10 4:44 ` query Andrea 'Fyre Wyzard' Bocci
2001-12-06 1:37 Query Bansal, Shashank
2001-12-06 1:45 ` Query Bansal, Shashank
2001-12-06 5:19 ` Query Jack Lloyd
2001-12-06 7:44 ` Query Tim Prince
2001-01-22 6:20 Query MNShukla
2001-01-22 6:27 ` Query Richard Earnshaw
2001-01-22 12:28 ` Query Philip Blundell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3ADFC019.451A85D5@cirrus.stpp.soft.net \
--to=mnshukla@cirrus.stpp.soft.net \
--cc=gcc@gcc.gnu.org \
--cc=nickc@cambridge.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).