LD_LIBRARY_PATH issue

Thomas De Schampheleire patrickdepinguin+uclibc at gmail.com
Wed Nov 2 11:10:30 UTC 2011


Hi,

On Wed, Nov 2, 2011 at 11:21 AM, Mahanteshwari Hiremath
<Mahanteshwari.Hiremath at lnties.com> wrote:
> I see it is over riding my native toll commands.
> suggest me how can i safely set this LD_LIBRARY_PATH, so that i can use native libraries and commands as well.

Could you try to explain what you are doing in a bit more detail?
Are you building for the same machine on which you build, or are you
building for another target?

Normally, you shouldn't need LD_LIBRARY_PATH at all. What happens if
you just run your application?

You may want to use chroot to create a temporary environment in which
the 'buildroot/output/target' directory is at /, so that only those
libraries can be found, see http://linux.die.net/man/1/chroot.
For example:
chroot /path/to/buildroot/output/target /bin/sh

Best regards,
Thomas


More information about the uClibc mailing list