This is the mail archive of the
mailing list for the binutils project.
Re: glibc 2.1 and gabi
- To: Geoff Keating <geoffk at cygnus dot com>
- Subject: Re: glibc 2.1 and gabi
- From: "H . J . Lu" <hjl at lucon dot org>
- Date: Thu, 20 Jul 2000 13:57:29 -0700
- Cc: libc-hacker at sourceware dot cygnus dot com,binutils at sourceware dot cygnus dot com, ian at zembu dot com, nick at lucon dot org
- References: <20000720114229.A6435@lucon.org> <200007202022.NAA15027@localhost.cygnus.com>
On Thu, Jul 20, 2000 at 01:22:31PM -0700, Geoff Keating wrote:
> > Date: Thu, 20 Jul 2000 11:42:29 -0700
> > From: "H . J . Lu" <firstname.lastname@example.org>
> > Hi,
> > 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 :-).
> I don't understand your problem. You're creating an executable that
> uses new features of ELF which were not implemented in glibc 2.1.
> glibc 2.1 complains that it doesn't understand this executable. The
> obvious fix is to make glibc 2.2 understand the executable, then use
> glibc 2.2. Why do you want to do something different?
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.