On 01/18/2016 10:14 PM, Przemek Klosowski wrote:
On Mon, Jan 18, 2016 at 9:57 PM, William Hermans <[email protected]> wrote:
Also, using LD_LIBRARY_PATH in this manner is just flat out wrong. If you
have a shared library file, put it in the correct directory to begin with.
On Mon, Jan 18, 2016 at 6:24 PM, Mike <[email protected]> wrote:
export LD_LIBRARY_PATH="../../library/libEBBLibrary.so:$LD_LIBRARY_PATH"
Why do you think it's wrong? The point of LD_LIBRARY_PATH is to
collect all the places you might have shared libs, whether system or
application or private.
There's even another trick, using LD_PRELOAD to force certain library
into the image to override symbols from e.g. system libraries; this
works great for debugging.
BTW, if you need to add a library file or directory to a single
application, I'd recommend just setting the environment for this
single command rather than exporting it for general use:
LD_PRELOAD=/home/user/proj/lib/libdebug.so LCDApp
I'm not going debate the use of LD_LIBRARY_PATH, as an admin all I'll
say is it's terribly abused and a security nightmare if not used properly.
Your example may well solve his issue and is a workable solution. Noting
the the path is absolute and not relative...
Mike
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
