First, apologies if these topics have been beaten to death. I have
had a hard time staying subscribed to this list as it seemed to bounce
around from server to server, and can't seem to find any recent
archives.
Is it possible to specify a path for System.loadLibrary()? I have not
been able to get LD_LIBRARY_PATH to have any effect. I hacked a
version of java.lang.Runtime that dumps the result of the
initializeLinkerInternal call to stderr and it appears to be
consistently empty regardless of the value of LD_LIBRARY_PATH.
I have also been having problems using javah when .zip files are in
the classpath, entailing complaints about inability to resolve various
symbols such as __muldi3. I suspect this is a result of not having
-lgcc in the build line when building the shared libraries (notably
libjava and libzip). I have not been able to test this theory, not
having access to the original JDK source. ldd -r on libjava.so
complains about missing libgcc symbols on both my Debian 1.3.1 (libc5
5.4.33) and pre-2.0 (libc6 2.0.6).
I appreciate any insight or advice anyone can provide.
--
Robert Coie
Implementor, Intrigue Ltd.
