[Tfug] Strange ld behavior

[R351574NC3]

This should not make the difference if /usr/java/j2sdk1.4.0/jre/lib/i386 
and /usr/java/j2sdk1.4.0/jre/lib/i386/{server,client} are in your 
/etc/ld.so.conf, but try adding those directories to LD_LIBRARY_PATH and 
see if that does anything. Also, ldd -v can be someone helpful as it 
outputs "verbose" information.

I was looking at a server at work just a few moments ago and it had the 
same issue right down to the directory structure. I created an 
ld.so.conf and ld.so.cache in my home directory and tried testing some 
things. Somehow LD_LIBRARY_PATH is what fixed my problem.  My problem 
was that I had an 2 conf files. One was for a.out binaries and one was 
for elf binaries. There was some confusion between the two. Don't know 
if it is the same problem you are having though.

-Leo

James Hood wrote:

>>If you you haven't, I would first try ldconfig -v to see if ldconfig
>>is indeed finding either file at all. It will tell you where it is
>>finding them and if there are any conflicts also.
>>    
>>
>
>Tried it, the output shows:
>
>/usr/java/j2sdk1.4.0/jre/lib/i386: (hwcap: 0x1000000000000)
>	libzip.so -> libzip.so
>	libverify.so ->libverify.so
>	...
>	libjava.so -> libjava.so
>	...
>
>It doesn't mention anything about any conflicts and the libverify.so it
>found is in the proper directory. Yet when I do 'ldd libjava.so' (in the
>java directory) I still get that libverify.so is not found. Weird!
>
>James
>_______________________________________________
>tfug mailing list
>tfug@tfug.org
>https://www.tfug.org/mailman/listinfo/tfug
>  
>