This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Marking JNI funtions extern

From: Mark Wielaard <mark at klomp dot org>
To: Andrew Haley <aph at redhat dot com>
Cc: tromey at redhat dot com, java at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
Date: Fri, 21 May 2004 13:11:11 +0200
Subject: Re: Marking JNI funtions extern
References: <1085053681.17363.421.camel@elsschot.wildebeest.org> <873c5vqewx.fsf@fleche.redhat.com> <1085136365.17367.541.camel@elsschot.wildebeest.org> <16557.57563.524237.780258@cuddles.cambridge.redhat.com>

Hi,

On Fri, 2004-05-21 at 12:58, Andrew Haley wrote:
> Mark Wielaard writes:
>  > 2004-05-21  Mark Wielaard  <mark@klomp.org>
>  > 
>  >         * gjavah.c (print_stub_or_jni): Mark functions only JNIEXPORT, not
>  >         extern.
>  > 
>  > The extern function modifiers were confusing the kaffe build process.
> 
> OK,

Thanks. Committed.

> but I'm curious.  In what way was this confusing the Kaffe build process?

In certain cases they define JNIEXPORT as "extern" and "extern extern"
isn't valid. I actually think they should not define JNIEXPORT as
"extern" though, so next up is convincing them to fix their jni.h (or
adopt the libgcj/GNU Classpath one of course).

Cheers,

Mark

Attachment: signature.asc
Description: This is a digitally signed message part

Follow-Ups:
- Re: Marking JNI funtions extern
  - From: Ranjit Mathew

References:
- Marking JNI funtions extern
  - From: Mark Wielaard
- Re: Marking JNI funtions extern
  - From: Tom Tromey
- Re: Marking JNI funtions extern
  - From: Mark Wielaard
- Re: Marking JNI funtions extern
  - From: Andrew Haley

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]