[Bug java/28153] Under Windows Xp the generated JNI headers need to have a '_' prepended for each function.

2007-01-30 Thread tromey at gcc dot gnu dot org
--- Comment #9 from tromey at gcc dot gnu dot org 2007-01-30 21:03 --- This was fixed a while ago. -- tromey at gcc dot gnu dot org changed: What|Removed |Added

[Bug java/28153] Under Windows Xp the generated JNI headers need to have a '_' prepended for each function.

2006-08-07 Thread tromey at gcc dot gnu dot org
--- Comment #8 from tromey at gcc dot gnu dot org 2006-08-07 16:30 --- I think comment #3 explains the problem. So, this is either a more general GCC bug, or it is not a bug at all. In any case it isn't a gcj problem :-) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28153

[Bug java/28153] Under Windows Xp the generated JNI headers need to have a '_' prepended for each function.

2006-07-06 Thread bcmpinc at hotmail dot com
--- Comment #7 from bcmpinc at hotmail dot com 2006-07-06 12:37 --- extern JNIEXPORT void JNICALL Java_JavaSide_sayHello (JNIEnv *env, jobject); After preprossesing this becomes: __attribute__((dllexport)) void __attribute__((__stdcall__)) Java_sample_myNative (JNIEnv *, jobject, js

[Bug java/28153] Under Windows Xp the generated JNI headers need to have a '_' prepended for each function.

2006-07-05 Thread tromey at gcc dot gnu dot org
--- Comment #6 from tromey at gcc dot gnu dot org 2006-07-06 00:05 --- Any word on this? -- tromey at gcc dot gnu dot org changed: What|Removed |Added Status|

[Bug java/28153] Under Windows Xp the generated JNI headers need to have a '_' prepended for each function.

2006-06-26 Thread tromey at gcc dot gnu dot org
--- Comment #5 from tromey at gcc dot gnu dot org 2006-06-27 03:20 --- Yeah, jni.cc handles the lookup side of things. The declaration side of things in user JNI code should be handled by jni_md.h. It has a bunch of win32-specific code which boils down to: #define JNIIMPORT__d

[Bug java/28153] Under Windows Xp the generated JNI headers need to have a '_' prepended for each function.

2006-06-26 Thread dannysmith at users dot sourceforge dot net
--- Comment #4 from dannysmith at users dot sourceforge dot net 2006-06-26 22:26 --- (In reply to comment #3) > I think you may be running into a compiler (MSVC vs GNUC) difference between > handling of __stdcall (==JNICALL) symbols. Um, and this should all be taken care of by the #ifd

[Bug java/28153] Under Windows Xp the generated JNI headers need to have a '_' prepended for each function.

2006-06-26 Thread dannysmith at users dot sourceforge dot net
--- Comment #3 from dannysmith at users dot sourceforge dot net 2006-06-26 21:21 --- I think you may be running into a compiler (MSVC vs GNUC) difference between handling of __stdcall (==JNICALL) symbols. For a function void __stdcall foo (int), both MSVC and GNUC generate an assemble

[Bug java/28153] Under Windows Xp the generated JNI headers need to have a '_' prepended for each function.

2006-06-26 Thread bcmpinc at hotmail dot com
--- Comment #2 from bcmpinc at hotmail dot com 2006-06-26 21:01 --- (In reply to comment #1) > Does the JDK's javah put that "_" into the generated header? No, JDK's javah creates a header equivalent to the header created by 'gcjh -jni'. > I suspect that you are seeing a problem with th

[Bug java/28153] Under Windows Xp the generated JNI headers need to have a '_' prepended for each function.

2006-06-26 Thread tromey at gcc dot gnu dot org
--- Comment #1 from tromey at gcc dot gnu dot org 2006-06-26 17:22 --- Does the JDK's javah put that "_" into the generated header? I suspect that you are seeing a problem with the C compiler, not a problem with JNI header generation. In particular I think that "_", most likely, should