PATCH to fix STDCALL in jni.cc
Mohan Embar
gnustuff@thisiscool.com
Thu Jun 24 16:03:00 GMT 2004
Hi All,
>Hi Per,
>
>>As a follow-up to:
>>http://gcc.gnu.org/ml/java/2004-06/msg00338.html
>>this patch is needed to build libjava on MinGW.
>>Unless I hear a reason not to, I'll check it into
>>mainline in a few days.
>
>I have a sinking feeling that this is related to
>this:
>
>http://gcc.gnu.org/ml/java/2004-06/msg00295.html
>
>I haven't had time to look into this (and am also
>afraid it's over my head because it might be a compiler
>bug), but even after your patch, I get a boatload
>of unresolved references when I try to build a simple
>HelloWorld application. I've attached the error log.
>
>After you apply your patch, are you actually able to
>build anything with your MinGW compiler?
FWIW: I've attached the output of "dumpbin /symbols jni.o"
to this email. (There's probably a free utility to do the same
thing, but I don't know what it is.) As you can see, there
are a boatload of undefined symbols. This is after Per's
patch; the situation is pretty much the same before the
patch too. I initially thought that the template functions
were the culprit, but there are functions like
_Jv_JNI_DestroyJavaVM that are being reported as undefined
too. (Could it have anything to do with the initial underscore??)
-- Mohan
http://www.thisiscool.com/
http://www.animalsong.org/
More information about the Java-patches
mailing list