|
Home > Archive > Unix questions > March 2004 > 'Path for the shared libraries which I do not have direct dependency' also in LD_LIBRA
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
'Path for the shared libraries which I do not have direct dependency' also in LD_LIBRA
|
|
| qazmlp 2004-03-24, 10:39 am |
| I have a shared library libFirst.so
I have a shared library libSecond.so which has dependency libFirst.so.
Hence, while producing the libSecond.so, I have to add the path to
libFirst.so
in the LD_LIBRARY_PATH
I have a shared library libThird.so which has dependency only on
libSecond.so.
So, I mentioned the path to only libSecond.so in the LD_LIBRARY_PATH
while producing
libThird.so.
But, the linker reports error pointing at the symbols in libFirst.so
After adding the path to libFirst.so also in the LD_LIBRARY_PATH, the
error disappears.
I am wondering why such a requirement of adding the path of some other
shared libraries also is required when my library libThird.so does not
have a direct dependency on them.
Kindly clarify!
| |
| qazmlp 2004-03-24, 8:36 pm |
| Chuck Dillon <cdillon@nimblegen.com> wrote in message news:<c3s731$1tc$1@grandcanyon.binc.net>...
> qazmlp wrote:
>
> The default linker behavior when linking a program or .so is to fully
> resolve all symbols including the dependencies in .so's indirectly
> referenced.
If default behaviour is so, is it possible to change such that, we do
not to give the path for indirect dependencies?
>
> Don't rely on LD_LIBRARY_PATH to resolve link time references. Specify
> the library locations on the compiler (or linker) command line (e.g.
> -L<path to non-system-standard-libraries> ).
Ok, Thanks!
|
|
|
|
|