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: Mark Mitchell <mark at codesourcery dot com>
- Subject: Re: ia64 libjava java-signal.h build failure
- From: Tom Tromey <tromey at redhat dot com>
- Date: 19 Apr 2001 19:24:30 -0600
- Cc: aoliva at redhat dot com, wilson at cygnus dot com, gcc-bugs at gcc dot gnu dot org, java at gcc dot gnu dot org, aph at redhat dot com
- References: <or66g0pv3e.fsf@guarana.lsd.ic.unicamp.br> <20010419140741B.mitchell@codesourcery.com>
- Reply-To: tromey at redhat dot com
Alexandre> the rest of the development snapshot. I'm all for
Alexandre> re-enabling it by default.
Mark> I'm not. It's just too risky at this point.
What do you mean? What is the risk?
FWIW I've bootstrapped and run `check-target-libjava' for gcc3+java on
x86 Linux, PPC Linux, and Solaris regularly (some more regularly than
others) for the last few weeks.
Tom