[uClibc] ld.so loading "false" libs

Joakim Tjernlund Joakim.Tjernlund at lumentis.se
Sun Sep 26 12:13:11 UTC 2004


> On Sat, 25 Sep 2004, Joakim Tjernlund wrote:
> 
> > > Could this be related to the fact that running ldd it shows all the time 
> > > (0x00000000) after the used lib (as opposed to glibc's ldd, where there 
> > > are different values, I think telling us which lib is used (some 
> > > kind of versioning)?
> > 
> > That is the load address for the lib. On PPC ldd /bin/busubox shows:
> >         libm.so.0 => /lib/libm.so.0 (0x30016000)
> >         libcrypt.so.0 => /lib/libcrypt.so.0 (0x3003c000)
> >         libc.so.0 => /lib/libc.so.0 (0x30060000)
> >         ld-uClibc.so.0 => /lib/ld-uClibc.so.0 (0x30000000)
> 
> my arch is x86, why do I have 0x00000000?

You probably need to compile uClibc with __LDSO_LDD_SUPPORT #defined

 Jocke



More information about the uClibc mailing list