Can't find path for shared library

[Adolf Koenig]

Hi,

for a new version of splus (7.0) we had to install a new Version of JAVA JRE (1.5) and for this a bunch of patches on HP-UX 11i.

Now we get the errormessages

/usr/lib/dld.sl: Can't find path for shared library: libjvm.sl
/usr/lib/dld.sl: No such file or directory

with the new and the older versions of splus (which worked before).

I tried to explicitly set SHLIB_PATH and checked the binary of the program with chatr to see, whether it's enabled. I even copied the libjvm.sl of the splus package to /usr/lib, so it should be findable, but no success. Which other conditions are known to cause such a message?

[Peter Godron]

Hi,
did you just set the SHLIB_PATH or did you also export it ?
Did you check all your other java related variables (JAVA_HOME,CLASSPATH..)?
Did you check all your links from your new java jre install ?
See:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=739519

If you found these comments useful, please see:
http://forums1.itrc.hp.com/service/forums/helptips.do?#33

[Adolf Koenig]

Hi Peter

I had already exported the SHLIB_PATH
and now defined and exported
CLASSPATH=/opt/java1.5/jre/lib
JAVA_BINDIR=/opt/java1.5/jre/bin
JAVA_HOME=/opt/java1.5/jre/
JAVA_ROOT=/opt/java1.5/jre/
JRE_HOME=/opt/java1.5/jre/
These were all the Java-related variables I found.
I also set LD_LIBRARY_PATH and LIBPATH as was
recommended in another thread to a similar problem

No changes in the behaviour so far.

I found something maybe important in the coredump to this error:
/usr/lib/dld.sl
ERROR: mmap failed for dld
ERROR: mmap failed for TSD

But I cannot judge, which error is the consequence of the other

I had already looked into the link you gave me, but it didn't help.

I just discovered, that the splus-java-executable
is PA-RISC1.1 shared executable dynamically linked
and the JRE-libs are in directories called
..PA_RISC2.0W... and
..PA_RISC2.0...
Does this go together? Maybe I installed the wrong JAVA-Kit.

[Adolf Koenig]

The problem is solved now.
It turned out that one of the patches (PHSS_33037) caused this error under certain circumstances. Meanwhile the patch is replaced by PHSS_35379 and with this patch it's ok.