Re: build error (2)

[Tom Tromey <tromey at cygnus dot com>]

>>>>> "Tom" == Tom Williams <Tom.Williams@diversifiedsoftware.com> writes:

Tom> Of course, this has nothing to do with libgcj or gcj, but I
Tom> thought I would vent just a tad..... :-)

Stability and the relative inaccessibility of gcj and libgcj have been
problems for a long time now.

This is something we're hoping to fix with gcc 3.0.  Alex is working
madly to get libgcj into the gcc tree.  He's also doing the new ABI
work in gcj (I'll probably do the runtime side once he's determined
how he wants to handle vtable layout and the like).

Hopefully gcc 3.0 will be stable enough and deployed widely enough
that we can recommend it to almost everybody.

Also I hope that gcc 3.1, 3.2, etc, don't take as long to come out as
3.0 did.  That will let us release library improvements and front end
bug fixes on a more regular schedule.


You might have heard that there is now going to be a gcc 2.95.3
release.  I'm inclined to simpy ignore it.  If it had been started 6
months ago I would have said that we should put the new front end into
it, but now that just seems like make-work, especially given that
we're a bit behind on the gcc 3.0 work.  Any comments on this?

Tom