Library path problem
walter harms
wharms at bfs.de
Sun Jul 30 15:00:06 UTC 2006
with ldd you can see libraries with full path.
e.g.:
ldd /bin/ls
librt.so.1 => /lib/librt.so.1 (0x4002b000)
libacl.so.1 => /lib/libacl.so.1 (0x4003c000)
libc.so.6 => /lib/libc.so.6 (0x40042000)
libpthread.so.0 => /lib/libpthread.so.0 (0x40160000)
libattr.so.1 => /lib/libattr.so.1 (0x40175000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
make sure they are build with path correct in your real system and not
in your crosscompile environment.
btw: do not forget to run lddconfig the the changes you make are noticed!
re,
wh
Val V. wrote:
> Hi,
>
> I am running kernel 2.4.22-pre8 and busybox 1.00-pre2 (static) on
> embedded EP852T board (PowerPC). I built both with GCC-2.95.3 and
> GLIBC-2.2.1 (the toolchain was part of the Embeded Planet BSP). The root
> file system is NFS mounted.
> If the symbolic links to the library files in /lib are set to the full
> path (ld.so.2->/ep852/rootfs/lib/ld-2.1.1.so, etc) Busybox works fine,
> but I cannot run any dynamically linked apps I build for testing.
> If I change the symbolic links so they would not contain the full path
> (ld.so.2->ld-2.2.1.so) my test apps start working, but several of the
> Busybox applets stop working (ps, ping, etc). I also thried to use a
> ramdisk instead of NFS, but the results were the same. I also tried
> Busybox 1.2.0 - did not make any diference.
> I was wondering if somebody would be able to give me a clue about what
> am I doing wrong?
>
> Thanks,
>
> Valiaka
>
>
> _______________________________________________
> busybox mailing list
> busybox at busybox.net
> http://busybox.net/cgi-bin/mailman/listinfo/busybox
>
>
>
More information about the busybox
mailing list