This is the mail archive of the
mailing list for the Java project.
Re: "This configuration is not supported ..."
- To: Alexandre Oliva <aoliva at redhat dot com>
- Subject: Re: "This configuration is not supported ..."
- From: Bryce McKinlay <bryce at albatross dot co dot nz>
- Date: Sat, 13 Jan 2001 15:53:48 +1300
- CC: Joe Buck <jbuck at racerx dot synopsys dot com>, gcc at gcc dot gnu dot org, java-discuss at sources dot redhat dot com
- References: <200101130004.QAA26868@racerx.synopsys.com> <email@example.com>
Alexandre Oliva wrote:
> On Jan 12, 2001, Joe Buck <firstname.lastname@example.org> wrote:
> > However, the compiler bootstraps OK. Why these messages, and what is
> > missing?
> Java had been disabled by default until it became compatible with the
> v3 ABI. I think the compatibility bits are already in, so it's
> probably ok to re-enable it, right?
Alex's V3 ABI changes arn't in yet. There's one small issue that still
needs to be resolved. Once the changes are in, we'll enable libgcj for
linux platforms. Other platforms can be enabled once they're working
> Anyway, even after this change, you'll still see that libchill is
> disabled, because the Chill language is disabled by default. Maybe
> languages disabled by default shouldn't cause such a message to be
Sounds reasonable to me. The "configuration not supported" message
certainly doesn't seem appropriate for the libgcj case...
[ bryce ]