🚀 go-pugleaf

E Steel <steel@tis4000.com> wrote:
[snip]
> All fies in the shared library were created with the gcc compiler with
> the -fpic flag set and -G on the ld command. The library is found, but
> when I reference one of the jni methods, snapInit, I get an "Unsatisfied
> link error snapInit", like it can not be found in the share library.
> However, when I do a Unix nm on the shared library, I can see the
> decorated name for this function in there. I hope I have given enough
> info. Any suggestions will be greatly appreciated.

Two things to check for first:

  Does 'ldd -r libwhatever.so' report any undefined symbols?  If it does,
it will cause unsatisfied link errors when the JVM executes the loadLibrary()
method.  I found that it's important to make sure you compile with gcc's
-shared option.  This is the only sort of library the JVM on linux will load,
and since the Linux JVM is a port of the Solaris JVM, I assume the Solaris JVM
has the same requirement.  (That's what my JNI references say as well, but I
haven't built any JNI on Solaris myself yet.)

  The other thing to check is that you've remembered to use the JNIenv pointer
to access your JNI methods within your C code.  If I write a JNI call
and forget to use that pointer, it compiles just fine, and the library
links okay, but ldd -r will show that method as an unresolved reference
and the JVM will throw the Unsatisfied link exception.

For example, if I am supposed to write

    const char *str = (*env)->GetStringUTFChars(env, input, 0);

But I mistakenly write

    const char *str = GetStringUTFChars(env, input, 0);
  
Then I'll get that same error.
-- 
Joi Ellis (TeamB) 
No direct email, please.
For best results, post on news server newsgroups.borland.com!