Hi all 
a major customer has linked their binary this way:

   CC fn_test_exe.o -R /fnsw/lib/shobj libfn_test_shlib.so 

next they run crle to tell the linker to find the libs not in /fnsw/lib/shobj
but in  /apps002/fnsw/lib/shobj/fixed-libs/ (don't ask why they're doing this):

 crle -c fn.conf

 Configuration file [version 4]: fn.conf  [ RTLD_REL_RELATIVE ]
 Default Library Path (ELF):   /usr/lib  (system default)
 Trusted Directories (ELF):    /usr/lib/secure  (system default)

 Memory Reservation:     ff1d0000 - ff1e2000 (12000 bytes)

 Directory: /apps002/fnsw/lib/shobj
 libfn_test_shlib.so   (alternate:
 /apps002/fnsw/lib/shobj/fixed-libs/libfn_test_shlib.so)

 Directory: .
 libfn_test_shlib.so   (alternate:
 /apps002/fnsw/lib/shobj/fixed-libs/libfn_test_shlib.so)

 Command line:
 crle -c fn.conf -o /apps002/fnsw/lib/shobj/fixed-libs -I
 ./libfn_test_shlib.so
 
They set their LD_LIBRARY_PATH also like this:

         LD_LIBRARY_PATH=/fnsw/lib/shobj/fixed-libs:/fnsw/lib/shobj

However, no library is loaded from /fnsw/lib/shobj/fixed-libs,
during run time. Here is the ldd output:

/fnsw/lib/shobj/libvwalloc.so
/fnsw/lib/shobj/libvwfnbase.so

All the libs get loaded from /fnsw/lib/shobj.
What do you think could be causing this?
I thought LD_LIBRARY_PATH took precedence over -R linker option?

Thanks much.
Haroon
-- 
This message posted from opensolaris.org

Reply via email to