Bug 706 - Wrong ldd: glibc ldd can't handle libc5 apps
Wrong ldd: glibc ldd can't handle libc5 apps
Product: Red Hat Linux
Classification: Retired
Component: glibc (Show other bugs)
All Linux
high Severity medium
: ---
: ---
Assigned To: Cristian Gafton
Depends On:
  Show dependency treegraph
Reported: 1999-01-06 10:43 EST by Alan Shutko
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-03-22 14:21:30 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Alan Shutko 1999-01-06 10:43:37 EST
glibc and ld.so both contain ldd.  The ldd in glibc doesn't
treat libc5-linked applications correctly, but the ld.so ldd
does.  For example, on a (working) WP7 installation, glibc
ldd reports

        libXt.so.6 => /usr/X11R6/lib/libXt.so.6 (0x40006000)
        libX11.so.6 => /usr/X11R6/lib/libX11.so.6
        libXpm.so.4 => /usr/X11R6/lib/libXpm.so.4
        libm.so.5 => not found
        libc.so.5 => not found
        libSM.so.6 => /usr/X11R6/lib/libSM.so.6 (0x40100000)
        libICE.so.6 => /usr/X11R6/lib/libICE.so.6
        libc.so.6 => /lib/libc.so.6 (0x4011e000)
        /lib/ld-linux.so.1 => /lib/ld-linux.so.2

but ld.so ldd and strace both report that it is correctly
linking against the libc5 libraries.  This poses a
significant problem in diagnosing problems with libc5
applications like WordPerfect, as the tool people depend on
to see what libraries are being used is wrong.
Comment 1 Preston Brown 1999-03-22 14:21:59 EST
the backwards compatibility hacks to get libc5 binaries running are
the not the cleanest things in the world, but they work.

Our glibc expert (Cristian Gafton) believes that the ldd that we are
shipping is much more reliable and advanced than the ldd you are
referring to in ld.so, which is why we use it.

Note You need to log in before you can comment on or make changes to this bug.