Bug 20090

Summary: ldd fails on (libc5) binaries
Product: [Retired] Red Hat Linux Reporter: ronny
Component: ld.soAssignee: Jakub Jelinek <jakub>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2000-10-31 11:35:24 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description ronny 2000-10-31 11:35:22 UTC 
ldd ./foo
/usr/bin/ldd: ./foo: No such file or directory

While a rh6.2 reports
ldd ./foo
        libncurses.so.3.0 => /usr/i486-linux-libc5/lib/libncurses.so.3.0
(0x4000c000)
        libg++.so.27 => /usr/i486-linux-libc5/lib/libg++.so.27 (0x40047000)
        libc.so.5 => /usr/i486-linux-libc5/lib/libc.so.5 (0x4007f000)
        libstdc++.so.27 => /usr/i486-linux-libc5/lib/libstdc++.so.27
(0x40148000)
        libm.so.5 => /usr/i486-linux-libc5/lib/libm.so.5 (0x4017a000)

Some/all of the above libraries are nonexistant on the rh7, but then ldd
should report that, shouldn't it? (sarcastic)

Happens on several binaries which have in common the libc5 library. The
binary above can be found at ftp://ftp.axis.se/pub/users/ronny/foo
Comment 1 Jakub Jelinek 2000-10-31 11:40:57 UTC 
ldd for ELF programs works by executing the program with special environment
variables so that the dynamic linker can print the information.
But you miss the dynamic linker (/lib/ld-linux.so.1) which we no longer ship,
so ldd cannot do anything about it.
You can install ld.so package from RHL6.2 if you want libc5 compatibility.
Comment 2 openshift-github-bot 2016-01-27 16:58:54 UTC 
Commit pushed to master at https://github.com/openshift/origin

https://github.com/openshift/origin/commit/7d76e2e6880c1c9dfddb37e5c270bc1930c059a6
UPSTREAM: <carry>: allow hostDNS to be included along with ClusterDNS setting

Reverts behavior change made in k8s PR 18089

Carry until k8s issue 20090 is resolved and provides a way to opt out of clusterDNS-only behavior

This was changed in k8s PR 18089