[BusyBox] busybox & uclibc "relinking"
Christian Zoffoli
merlin at studiobz.it
Wed May 21 15:28:18 UTC 2003
[cut]
>
>
> Wait a minit. The part of ldd's output which follows after "=>" shows the
> path where the lib on the left side of "=>" is actually resolved. If you
> take your binary to a machine where uClibc is installed in
> /foo/lib/uClibc, then you will see ldd showing:
>
> libc.so.0 => /foo/lib/uClibc/libc.so.0
> /usr/lib/ld-uClibc.so.0 => not found
>
> -- as the latter one is an absolute path and cannot be resolved. So in
> your case, the path /build/uClibc/usr/lib is not hardlinked to your
> binary, so I think there is no problem, but you will not see
>
> libc.so.0 => /usr/lib/libc.so.0 (0x0x40006000)
> ld-uClibc.so.0 => /usr/lib/ld-uClibc.so.0 (0x0x40000000)
>
> 'till you won't install uClibc to /usr/lib. But I think this is not wha
> you want.
but when I move the libraries to the the destination path (/usr/lib) and
busybox to /usr/bin on the target root filesystem it doesn't work. I
have to create /build/uClibc/usr/lib on the target filesystem to make it
work.
Any suggestion?
Regards,
Christian
More information about the busybox
mailing list