[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Compilation error - More Info
From: |
John Leuner |
Subject: |
Re: Compilation error - More Info |
Date: |
Mon, 29 Apr 2002 12:20:43 +0100 |
User-agent: |
Mutt/1.3.27i |
> I though it was plain old C.
> It's simply that I was using gcc 3.0.3 which allows this (I think it
> does C99 ?),
> so no error, so I thought it was ok C.
> R.
Yeah, I ran into this earlier with kissme too. People who are using older
compilers, eg 2.95.4 in debian/woody won't be able to compile.
I suspect we'll have to ask everyone who is changing native code to test with
the 2.9x compilers before they commit.
John Leuner
> Etienne M. Gagnon wrote:
>
> >On Sun, Apr 28, 2002 at 01:24:34PM -0400, Brian Jones wrote:
> >
> >>I disabled javax.swing in standard.omit. Having trouble compiling the
> >>java_nio.c recently added as well.
> >>
> >
> >I was planning to submit a bug report about it... java_nio.c contains
> >invalid C code. (C, unlike C++, does not support declarations between
> >statements). Maybe the author of java_nio.c was using a C++ compiler?
> >
> >Personal comment: I do not want to start a discussion thread about
> >this, but I think we should keep the JNI native part in plain C (as it
> >already is). Of course, C++ would be encouraged for the CNI stuff. :)
> >
> >Etienne
> >
>
>
>
>
> _______________________________________________
> Classpath mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/classpath
Re: Compilation error, Mark Wielaard, 2002/04/28