Please see Bug Id # 4345224.
The JNI user documentation (Release Notes) needs to be updated
to reflect the observations made in the Comments section of that
bug.
You can work with John Coomes or Dave Katleman to come up with
appropriate text for JNI section of the Release Notes.
(The text should, in essence, point out that JNI code can
either link against jre/lib/sparc/libjvm.so to get the default
Client JVM, or against jre/lib/sparc/server/libjvm.so to get the
Server JVM. In the latter case, the LD_LIBRARY_PATH should have
the VM-specific directory (jre/lib/`uname -p`/server/) preceding the
ISA-specific directory (jre/lib/`uname -p`).
The JNI user documentation (Release Notes) needs to be updated
to reflect the observations made in the Comments section of that
bug.
You can work with John Coomes or Dave Katleman to come up with
appropriate text for JNI section of the Release Notes.
(The text should, in essence, point out that JNI code can
either link against jre/lib/sparc/libjvm.so to get the default
Client JVM, or against jre/lib/sparc/server/libjvm.so to get the
Server JVM. In the latter case, the LD_LIBRARY_PATH should have
the VM-specific directory (jre/lib/`uname -p`/server/) preceding the
ISA-specific directory (jre/lib/`uname -p`).
- relates to
-
JDK-4345224 'jni compatibility symlink' can cause vm failures
-
- Closed
-