Most probably know this, but just in case, recent versions of Linux distributions provide a more modular way to control the library path via the /etc/ld.so.conf.d/ directory. For example I normally add path to oracle libraries by adding a file /etc/ld.so.conf.d/oracle-11.1-x86_64.conf with just a single line in it containing /usr/lib/oracle/11.1/client64/lib. I think you need to run ldconfig every time you modify the directory, but after that the library should be visible to all programs. You can add both 32 and 64 bit libraries this way. Not sure if this is immediately useful to help with this problem, but there it is. HTH, Martin "Eliot Miranda"<eliot.miranda@gmail.com> wrote:

The point is that LD_LIBRARY_PATH is used by dlopen, which is used by the VM's module loading mechanisms, etc, so that when e.g. the FFI tries to locate a library it will use LD_LIBRARY_PATH. So a) LD_LIBRARY_PATH needs to match the libraries the VM is linked against and b) LD_LIBRARY_PATH needs to include at least the standard places libraries will be found, which means a /lib and a /usr/lib.

HTH Eliot

...

Nahuel

-- best, Eliot