Re: classpath 0.10 and GCJ Version 3.3.3 20040215

[Mark Wielaard]

Hi Steve,

On Tue, 2004-07-20 at 23:27, Steven Augart wrote:
> I just accidentally tried to build Classpath 0.10 using GCJ (I was
> using an AIX machine, and I'd left Jikes out of my path).  The GCJ
> version is:
> 
>       gcj (GCC) 3.3.3 20040215 (release)
> 
> This gave the error:
> 
>      /usr/gnu/bin/gcj --bootclasspath '' --classpath 
> ../../classpath-0.10:../../classpath-0.10/external/jaxp/source:../vm/current:.:
>  -C -d . @classes
> ../../classpath-0.10/java/security/cert/X509Certificate.java:143: error: 
> Class `java.security.cert.X509Certificate' can't subclass interface 
> `java.security.Certificate'.
>    public abstract class X509Certificate extends Certificate implements 
> X509Extension
> 
> The "configure" script currently tests whether GCJ, if used, has at
> least version 3.3.  This doesn't seem to be adequate to get around
> the error.
> 
> Does anybody know what version of gcj we need to avoid this
> complaint?  We should update the configure script appropriately.

The release was tested against gcj (GCC) 3.3.4 (Debian 1:3.3.4-3) and
gcj CVS. Hopefully 3.3.4 is enough. But I see that Debian actually
includes a couple of patches for the compiler... One of which looks like
it was for the above issue. Darn. So you might actually need the 3.4 FSF
release.

The "official" policy is to make sure that the java source files can be
compiled against the latest official releases of gcj and jikes. (So if
gcj 3.4 and/or jikes 2.21 don't work, we have a bit of a problem.) But
in practice (in my case) this often means the last releases of gcj and
jikes in Debian. We do have a problem in any case since at least the
INSTALL/hacking-guide document doesn't explicitly say that (and the
configure script version check could indeed be updated).

Cheers,

Mark

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