From: "H . J . Lu" <hjl@lucon.org>
To: Nick Clifton <nickc@cygnus.com>
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 12:12:00 -0000 [thread overview]
Message-ID: <20000720121224.A6635@lucon.org> (raw)
In-Reply-To: <200007201906.MAA01571@elmo.cygnus.com>
On Thu, Jul 20, 2000 at 12:06:37PM -0700, Nick Clifton wrote:
> Hi H.J.
>
> : I added support for the new DT tags from the new gABI. However, glibc
> : 2.1 doesn't support them. I got
> :
> : BUG IN DYNAMIC LINKER ld.so: dynamic-link.h: 57: elf_get_dynamic_info: Assertion `! "bad dynamic tag"' failed!
> :
> : on DT_RUNPATH and DT_FLAGS when -Bsymbolic and -rpath are used. I
> : checked Solaris 2.7. Solaris ld.so doesn't complain DT_RUNPATH nor
> : DT_FLAGS which it doesn't know. I tend to think it is a glibc 2.1 bug.
> : But I don't want to break glibc 2.1. I'd like to add a new option
> : to ld to turn on the support for the new DT tags. Any suggestions?
> : I am thinking of "-z gabi" for lack of imagination :-).
>
> Do we need a switch, or can this be determined "magically" by
> examining the input files ?
No. It is a runtime thing. The same binaries run fine under glibc 2.2.
>
> If we need a switch, then I would suggest:
>
> --enable-dynamic-tags
>
> and:
>
> --no-enable-dynamic-tags
>
> which presumably would be the default.
>
Well, it is kind of misleading since glibc 2.1 does support dynamic
tags. It just doesn't support the unknown tags in certain range.
--enable-new-dynamic-tags
--no-enable-new-dynamic-tags
is better.
H.J.
next prev parent reply other threads:[~2000-07-20 12:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-20 12:06 Nick Clifton
2000-07-20 12:12 ` H . J . Lu [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-07-24 10:52 Nick Clifton
2000-07-20 14:12 Nick Clifton
2000-07-20 15:00 ` H . J . Lu
2000-07-20 13:17 Nick Clifton
2000-07-20 13:55 ` 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 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
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
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=20000720121224.A6635@lucon.org \
--to=hjl@lucon.org \
--cc=binutils@sourceware.cygnus.com \
--cc=ian@zembu.com \
--cc=libc-hacker@sourceware.cygnus.com \
--cc=nick@lucon.org \
--cc=nickc@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).