This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Patch: FYI: make jacks run again
- From: Tom Tromey <tromey at redhat dot com>
- To: GCC libjava patches <java-patches at gcc dot gnu dot org>
- Date: 04 Aug 2003 15:57:58 -0600
- Subject: Patch: FYI: make jacks run again
- Reply-to: tromey at redhat dot com
I'm checking this in on the trunk.
Without this, I always see "jacks failed", since jacks exits with
nonzero status. It is ok for us to just ignore this, since we parse
the output anyway.
Tom
Index: ChangeLog
from Tom Tromey <tromey@redhat.com>
* libjava.jacks/jacks.exp (gcj_jacks_run): Just ignore errors
from jacks.
Index: libjava.jacks/jacks.exp
===================================================================
RCS file: /cvs/gcc/gcc/libjava/testsuite/libjava.jacks/jacks.exp,v
retrieving revision 1.3
diff -u -r1.3 jacks.exp
--- libjava.jacks/jacks.exp 3 Feb 2003 16:20:30 -0000 1.3
+++ libjava.jacks/jacks.exp 4 Aug 2003 22:04:26 -0000
@@ -89,14 +89,11 @@
gcj_jacks_write gcj_setup
verbose "Running Jacks..."
- if {[catch {exec ./jacks gcj} msg]} {
- verbose "jacks invocation failure: $msg"
- fail "running jacks"
- } else {
- pass "running jacks"
+ # Just ignore error exits from the jacks program.
+ # It will always error exit for us, since don't completely pass.
+ catch {exec ./jacks gcj} msg
- gcj_jacks_parse logging/gcj.log
- }
+ gcj_jacks_parse logging/gcj.log
cd $here
}