On 01/18/2016 09:57 PM, William Hermans 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]
<mailto:[email protected]>> wrote:
<snipped>
root@beaglebone:~/exploringBB/chp09/LCDcharacter# export
LD_LIBRARY_PATH="../../library/libEBBLibrary.so:$LD_LIBRARY_PATH"
root@beaglebone:~/exploringBB/chp09/LCDcharacter# ./LCDApp
./LCDApp: error while loading shared libraries: libEBBLibrary.so:
cannot open shared object file: No such file or directory
I don't believe that LD_LIBRARY_PATH is searched in the manner
you're thinking in the last lines. If memory serves you need to
specify the full path from / i.e. absolute not relative.
Mike
Exactly my thoughts William. As a sys admin I've seen way to much LD_*
abuse not just LD_LIBRARY_PATH... It's really not that hard on Linux,
but if following other bad examples, well what can one say? Somewhere
out there is a great reference on GCC, G++ and using libraries. The
title or link eludes me now. Was from the UK somewhere I believe.
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.
