public inbox for java-prs@sourceware.org help / color / mirror / Atom feed
From: "tromey at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: java-prs@gcc.gnu.org Subject: [Bug java/28153] Under Windows Xp the generated JNI headers need to have a '_' prepended for each function. Date: Tue, 27 Jun 2006 03:20:00 -0000 [thread overview] Message-ID: <20060627032019.10733.qmail@sourceware.org> (raw) In-Reply-To: <bug-28153-12871@http.gcc.gnu.org/bugzilla/> ------- 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 __declspec(dllimport) #define JNIEXPORT __declspec(dllexport) #define JNICALL __stdcall It might be handy to see a small preprocessed source file. Perhaps you're picking up the wrong jni.h, jni_md.h, or perhaps the logic in jni_md.h is broken somehow. Oops, I just looked at your version... jni_md.h is not in 3.4. In 3.4 the same logic appears, only it is in jni.h. It is possible that we fixed some bugs in this area since 3.4. I don't remember. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28153
next prev parent reply other threads:[~2006-06-27 3:20 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-06-24 16:21 [Bug java/28153] New: " bcmpinc at hotmail dot com 2006-06-26 17:22 ` [Bug java/28153] " tromey at gcc dot gnu dot org 2006-06-26 21:01 ` bcmpinc at hotmail dot com 2006-06-26 21:21 ` dannysmith at users dot sourceforge dot net 2006-06-26 22:26 ` dannysmith at users dot sourceforge dot net 2006-06-27 3:20 ` tromey at gcc dot gnu dot org [this message] 2006-07-06 0:05 ` tromey at gcc dot gnu dot org 2006-07-06 12:37 ` bcmpinc at hotmail dot com 2006-08-07 16:30 ` tromey at gcc dot gnu dot org 2007-01-30 21:03 ` tromey at gcc dot gnu dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20060627032019.10733.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=java-prs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).