From: hjl@lucon.org (H.J. Lu)
To: ian@cygnus.com (Ian Lance Taylor)
Cc: gas2@cygnus.com, libc-hacker@cygnus.com
Subject: Re: Has anyone looked at ELF 4.1?
Date: Mon, 10 Aug 1998 16:54:00 -0000 [thread overview]
Message-ID: <m0z61lo-000391C@ocean.lucon.org> (raw)
In-Reply-To: <199808102051.QAA01721@subrogation.cygnus.com>
> As I read it, it's a bit different from the OLF proposal. SCO is
> defining EI_OSABI as indicating whether the file conforms to the
> standard ELF format. A value of 0 (ELFOSABI_SYSV) indicates that the
> file does conform. For EI_ABIVERSION, a conforming application must
> use 0. Our files do conform to the specification (I hope), so it is
> correct for us to use 0 for both.
>
> However, we could perhaps ask registry@sco.com to define
> ELFOSABI_LINUX, and define that as being the same as the standard, but
> using the Linux API. Similarly for other free operating systems.
>
The purpose of EI_OSABI and EI_ABIVERSION is to tag the OS and ABI.
I think we should register ELFOSABI_LINUX and define it as 1. It may
make many things easier for us. Right now, after I upgrade from
glibc 2.0 to 2.1, groff (man) no longer works since the C++ ABI in
glibc is changed.
--
H.J. Lu (hjl@gnu.org)
next prev parent reply other threads:[~1998-08-10 16:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-08-08 7:20 H.J. Lu
1998-08-08 10:02 ` Ulrich Drepper
1998-08-08 23:43 ` H.J. Lu
1998-08-10 13:51 ` Ian Lance Taylor
1998-08-10 16:54 ` H.J. Lu [this message]
1998-08-11 0:51 ` Roland McGrath
1998-08-11 9:22 ` Ian Lance Taylor
1998-08-16 18:10 ` H.J. Lu
1998-08-16 18:32 ` Ian Lance Taylor
1998-08-16 19:30 ` H.J. Lu
1998-08-16 20:01 ` Ian Lance Taylor
1998-08-17 13:14 ` Ulrich Drepper
1998-08-18 7:40 ` H.J. Lu
1998-08-18 8:04 ` Ulrich Drepper
1998-08-11 0:51 ` Roland McGrath
1998-08-11 20:43 ` Geoff Keating
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=m0z61lo-000391C@ocean.lucon.org \
--to=hjl@lucon.org \
--cc=gas2@cygnus.com \
--cc=ian@cygnus.com \
--cc=libc-hacker@cygnus.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).