in reply to Re^10: problem installing PLJava on Windows Vista
in thread problem installing PLJava on Windows Vista

Well ... I guess that's progress, at least :-)
Incidentally (for future reference), assuming you have ActivePerl, the easiest way to install both dmake and MinGW is to simply ppm install MinGW
That will give you all you need.

The 'dmake test' error has me baffled. Afaict, 'PLJava_start' is simply a function in PLJava.c, and I don't understand what java.lang.UnsatisfiedLinkError: PLJava_start is supposed to tell me.

As recommended by the test output, I've read "the Chapter on Dynamic Linking" in "the SWIG Java documentation for help" ... but it didn't. That documentation can be viewed online. If anyone has ideas on what to do at this point, then please share. (I don't mind trying to solve a good puzzle, but I'm not a java person at all.)

Cheers,
Rob

Replies are listed 'Best First'.
Re^12: problem installing PLJava on Windows Vista
by RASSyndrome (Novice) on Jun 17, 2009 at 03:48 UTC
    Same here. I'm a lot more up on Java than I am on Perl, but not to the point that I have any clue what to do here. Maybe I should take this to a Java forum at this point.

    Thanks for the help anyway, though.

[reply]
      One thing that did strike me as odd was that the actual java message we're getting is very light on diagnostic information. I wondered if the PLJava module was doing something to remove/conceal some of the diagnostic information, but I haven't yet gone looking to see if that's the case.

      Cheers,
      Rob
[reply]
        There's a smidge more information from "java test": 
        C:\Users\Shai\Documents\HadToDL\PLJava-0.04>java test
PLJava - Native code library failed to load. See the chapter on Dynami
+c Linking
Problems in the SWIG Java documentation for help.
java.lang.UnsatisfiedLinkError: perl5.PLJavaJNI.PLJava_start()I

        [download]

        Don't know if it helps all that much though. That perl5.PLJavaJNI.PLJava_start() is the culprit suggests that the problem is happening when Java tries to use the native function from the C component -- it fails at the border. Of the possible causes for this exception that the SWIG documentation lists, "unresolved symbols in the compiled C/C++ code" and "ensure that you are using the correct C/C++ compiler and linker combination and options for successful native library loading." would be the leading candidates -- the error occurs after the .dll loading happens. "java -verbose:jni test" doesn't say anything about unresolved symbols, though, and I can't seem to find anything about compiler-linker combinations in that SWIG Wiki... hmm.
[reply]
[d/l]

In Section Seekers of Perl Wisdom