This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: ia64 libjava java-signal.h build failure
- To: tromey at redhat dot com
- Subject: Re: ia64 libjava java-signal.h build failure
- From: Alexandre Oliva <aoliva at redhat dot com>
- Date: 19 Apr 2001 16:07:01 -0300
- Cc: Jim Wilson <wilson at cygnus dot com>, gcc-bugs at gcc dot gnu dot org, java at gcc dot gnu dot org, Andrew Haley <aph at redhat dot com>
- Organization: GCC Team, Red Hat
- References: <200104182203.PAA15986@wilson.cygnus.com><87k84hcyjd.fsf@creche.redhat.com>
On Apr 19, 2001, Tom Tromey <tromey@redhat.com> wrote:
> Why is Java not built by default on the branch?
> Does anyone know?
I guess it was disabled in the past just because it wasn't stable
enough and was hampering the testing of the rest of the development
snapshot. I'm all for re-enabling it by default.
> Is it hard to enable it by default for known good platforms?
Nope. Just comment out the `build_by_default=no' line in
gcc/java/config-lang.in, and it should build by default. The
top-level configure.in already disables libgcj on a number of
platforms, so that should be enough.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me