From: Geoff Keating <geoffk@cygnus.com>
To: hjl@lucon.org
Cc: libc-hacker@sourceware.cygnus.com,
binutils@sourceware.cygnus.com, ian@zembu.com, nick@lucon.org
Subject: Re: glibc 2.1 and gabi
Date: Thu, 20 Jul 2000 15:47:00 -0000 [thread overview]
Message-ID: <200007202246.PAA15150@localhost.cygnus.com> (raw)
In-Reply-To: <20000720135729.B6994@lucon.org>
> Date: Thu, 20 Jul 2000 13:57:29 -0700
> From: "H . J . Lu" <hjl@lucon.org>
> Cc: libc-hacker@sourceware.cygnus.com, binutils@sourceware.cygnus.com,
> ian@zembu.com, nick@lucon.org
> glibc 2.2 is ok. The problem is the existing glibc 2.1 systems. The
> binaries created by the new linker under glibc 2.1 may not run due
> to those new dtags. I just sent in a new patch which turns off the
> new dtag by default so that the linker can create the working binaries
> under glibc 2.1.
OK. That makes sense.
Ideally, you would want to only add the new tags when they make a
difference to how the executable should be treated. I don't know what
the new tags do so I don't know if this is possible.
--
- Geoffrey Keating <geoffk@cygnus.com>
next prev parent reply other threads:[~2000-07-20 15:47 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-20 11:42 H . J . Lu
2000-07-20 13:23 ` Geoff Keating
2000-07-20 13:57 ` H . J . Lu
2000-07-20 15:47 ` Geoff Keating [this message]
2000-07-20 15:52 ` H . J . Lu
2000-07-20 16:12 ` Geoff Keating
2000-07-20 17:10 ` H . J . Lu
2000-07-20 20:28 ` Geoff Keating
2000-07-20 21:15 ` H . J . Lu
2000-07-20 23:13 ` Geoff Keating
2000-07-20 23:22 ` H . J . Lu
2000-07-21 0:19 ` Mark Kettenis
2000-07-21 9:01 ` H . J . Lu
2000-07-21 9:07 ` H . J . Lu
2000-07-20 12:06 Nick Clifton
2000-07-20 12:12 ` H . J . Lu
2000-07-20 12:26 Nick Clifton
2000-07-20 12:41 ` H . J . Lu
2000-07-23 20:18 ` Andrew Cagney
2000-07-23 21:01 ` H . J . Lu
2000-07-20 13:17 Nick Clifton
2000-07-20 13:55 ` H . J . Lu
2000-07-20 14:12 Nick Clifton
2000-07-20 15:00 ` H . J . Lu
2000-07-24 10:52 Nick Clifton
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=200007202246.PAA15150@localhost.cygnus.com \
--to=geoffk@cygnus.com \
--cc=binutils@sourceware.cygnus.com \
--cc=hjl@lucon.org \
--cc=ian@zembu.com \
--cc=libc-hacker@sourceware.cygnus.com \
--cc=nick@lucon.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).