[uClibc] ldconfig/ldd problem tested against uClibc++

Erik Andersen andersen at codepoet.org
Wed Sep 8 03:11:03 UTC 2004


On Tue Sep 07, 2004 at 10:57:21PM -0400, Mike Frysinger wrote:
> On Tuesday 07 September 2004 06:07 pm, Mike Frysinger wrote:
> > this will happen when you run ldd against anything that isnt an executable
> > (i dont mean something that doesnt have +x as the permissions)
> 
> actually, lemme take this back
> 
> i just updated to the latest cvs and ldd doesnt spit that junk anymore:
> root at uclibc-amd64 0 lib # ldd libproc-3.2.3.so
>         libc.so.0 => libc.so.0 (0x00000000)
>         /lib/ld-uClibc.so.0 => /lib/ld-uClibc.so.0 (0x00000000)
> root at uclibc-amd64 0 lib #

The version of ldd in uClibc is somewhat special.  It attempts to
let the shared lib loader resolve things, iff that seems possible
(target is a executable for the correct architecture with the
specified shared lib loader present, etc, etc), otherwise it does
its best by grovelling about in the target's ELF headers, letting
it provide useful output even when used on cross-compiled apps,

 -Erik

--
Erik B. Andersen             http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--



More information about the uClibc mailing list