[uClibc]Re: [BusyBox] uClibc

Andreas Neuhaus andy at fasta.fh-dortmund.de
Mon May 28 15:53:09 UTC 2001


i tried the below on 5 different machines (i386 with different SuSE
versions: 7.1, 7.0, 6.4, 6.3. with 2.2.x and 2.4.x kernels) and the
resulting libuClibc-0.9.5.so was always linked against libNoVersion.so.1,
ld-uclibc.so.0, libc.so.0 and ld-linux.so.2... i checked out the current cvs
version and used the stock x86 config.

even if libc.so.6 is linked to libuClibc, when i compile an application
(like busybox) against that uClibc, ldd only shows ld-uclibc and libuclibc
and it runs fine on a system without libc.so.6.

i furthermore tried:

~ > strings uClibc/lib/libuClibc-0.9.5.so |grep \\.so
ld-uclibc.so.0
libc.so.0
~ > strings busybox/busybox |grep \\.so
/lib/ld-uclibc.so.0
libc.so.0
~ > strings /bin/ping |grep \\.so
/lib/ld-linux.so.2
libc.so.0

maybe my ldd is broken?

regards,
andreas neuhaus

> > This ldd shows something to be badly broken.  You should _never_ see
> > libc.so.6 and ld-uclibc.so.0 linked to the same executable.
> ~ > ldd uClibc/lib/libuClibc-0.9.5.so
> ldd: warning: you do not have execution permission for
> `uClibc/lib/libuClibc-0.9.5.so'
>         /lib/libNoVersion.so.1 => /lib/libNoVersion.so.1 (0x4002a000)
>         ld-uclibc.so.0 => not found
>         libc.so.6 => /lib/libc.so.6 (0x40037000)
>         /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x2aaaa000)







More information about the uClibc mailing list