This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: Help with ld.so debug output? (repost to group also)
- From: Mike Frysinger <vapier at gentoo dot org>
- To: john h <johnh dot nm at gmail dot com>
- Cc: libc-help at sourceware dot org
- Date: Wed, 13 May 2009 20:23:46 -0400
- Subject: Re: Help with ld.so debug output? (repost to group also)
- References: <a8299a810905131718j77d68b67n5b8cf16984bdc531@mail.gmail.com>
On Wednesday 13 May 2009 20:18:20 john h wrote:
> On Wed, May 13, 2009 at 6:13 PM, john h <johnh.nm@gmail.com> wrote:
> > On Wed, May 13, 2009 at 5:48 PM, Mike Frysinger <vapier@gentoo.org> wrote:
> >> On Wednesday 13 May 2009 19:32:41 john h wrote:
> >>> / # ./hello
> >>> ./hello: /lib/libm.so.6: version `GLIBC_2.1.3' not found (required by
> >>> /lib/libm. so.6)
> >>
> >> it means your binary was compiled against a newer version of glibc than
> >> the version found at runtime
> >> -mike
> >
> > It seems that our ld.so is not finding all the versions. We moved from
> > 2.3.3 of glibc to 2.3.6 and the old ld.so seems to work fine (even
> > with 2.3.6 so files), but the new ld.so gives this.
> >
> > We have a port of glibc to our custom processor.
> >
> > Is there somewhere that we need to update something so that the
> > versioning is right?
>
> Or is ld.so just broken and not built right?
i highly doubt it's related to the ld.so at all
> From 2.3.6 ld.so which is broken.
>
> ./hello: /lib/libm.so.6: version `GLIBC_2.1.3' not found (required by
> /lib/libm. so.6)
> libm.so.6 => /lib/libm.so.6 (0x4801c000)
sounds like your glibc 2.3.6 build is broken then. libm.so.6 should have
GLIBC_2.1.3 version info. use `readelf -V` on it to make sure.
-mike