[uClibc]Dynamic libuClibc.so woes

John Lombardo JohnLombardo at acm.org
Wed Mar 7 23:09:34 UTC 2001


> [andersen at slag silly]$ ldd ./hello
>         libuClibc.so.1 => /lib/libuClibc.so.1 (0x4000c000)
>         ld-linux.so.1 => /lib/ld-linux.so.1 (0x40039000)
> [andersen at slag silly]$ ls -sh ./hello
> 4.0k ./hello*
> [andersen at slag silly]$ ./hello
> hello world
>
>
> So there you have it.  An app compiled using a shared uClibc.  As
> can be seen
> by running 'ldd' it is linked automagicaly with the glibc shared library
> loader, so you don't need to do anything else to make it work.
> If this were

Afaikt, glibc does not produce a ld-linux.so.1, it produces a ld-linux.so.2.
If you're runnnig on RH 6.2, then the ld-linux.so.1 that you're running with
did not come from glibc at all, but from the ld.so package:

[root at jllinux libc]# rpm -q -f /lib/ld-linux.so.1
ld.so-1.9.5-1

John






More information about the uClibc mailing list