From: willy@ldl.fc.hp.com (Matthew Wilcox)
To: parisc-linux@parisc-linux.org
Subject: [parisc-linux] ELFOSABI_LINUX
Date: Tue, 1 May 2001 21:34:58 -0600 [thread overview]
Message-ID: <20010501213458.Y6063@zumpano.fc.hp.com> (raw)
Here's the current situation as I understand it.
* Binutils, when configured for an hppa-linux target, outputs binaries
with the EI_OSABI field set to ELFOSABI_LINUX instead of ELFOSABI_SYSV.
* The dynamic linker will refuse to link binaries for which the EI_OSABI
field doesn't match the expected values -- the patch Jes wrote last
december checks this field is set to either SYSV or LINUX, whereas
the standard check is just for SYSV. (note this is hppa-linux only
and affects no other architecture).
* The kernel does not currently check the EI_OSABI field.
The original discussion last November seemed to reach a resolution that
using this field to mark which ABI the OS implements was not the right
thing; instead this field marks ELF extensions that the ELF tools must
be aware of before manipulating this file.
Now, I'm not interested in digging up who did what when and why in order to
get us into this state. But we do have a problem here. Either we need to:
* Stay in violation of the interpretation of the spec proposed last
November. This implies adding the HPPA patch to glibc so ld.so will
recognise ELFOSABI_LINUX binaries.
* Change binutils to produce binaries without ELFOSABI_LINUX set. This
implies rebuilding every debian package we've built so far -- over
1100 source packages. This means we'd miss our deadline of shipping
at the end of May.
One subversive developer suggested a third alternative -- that we think up
& implement an extension to the ABI so we have to use ELFOSABI_LINUX :-)
Thoughts?
next reply other threads:[~2001-05-02 3:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-02 3:34 Matthew Wilcox [this message]
2001-05-02 23:47 ` [parisc-linux] ELFOSABI_LINUX amodra
2001-05-12 16:01 ` Jes Sorensen
-- strict thread matches above, loose matches on Subject: below --
2001-05-02 18:10 Cary Coutant
2001-05-04 3:11 ` Ulrich Drepper
2001-05-03 17:28 Cary Coutant
2001-05-04 17:05 Cary Coutant
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=20010501213458.Y6063@zumpano.fc.hp.com \
--to=willy@ldl.fc.hp.com \
--cc=parisc-linux@parisc-linux.org \
/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