This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Re: Patch: Run JNI tests using interpreter
- From: Ranjit Mathew <rmathew at gmail dot com>
- To: java-patches at gcc dot gnu dot org
- Date: Thu, 06 May 2004 11:22:59 +0530
- Subject: Re: Patch: Run JNI tests using interpreter
- References: <40996CDA.90204@redhat.com>
Bryce McKinlay wrote:
> + # libjava_find_gij will return `gij' if it couldn't find the
> + # program; in this case we want to skip the test.
You know, a safeguard like this seems necessary for
the testsuite as a whole - don't blindly run bare "gij"
or "gcj".
What happened some time back is that I tried out the
"make new_bootstrap" option and found out that quite
a lot of libjava tests were failing.
Turns out that the "gcj" being picked up was the
Red Hat installed 3.2.3 gcj on the system and not
the just built "gcj" because of a minor configury
issue with "new_bootstrap".
I have since removed the existing installation of
gcc-java-3.2.3, but it'll be better to avoid this
problem altogether.
Only if the testsuite is used independently of a GCC
build would this $PATH based picking up of "gcj"
make sense. Otherwise, I vote to remove this "feature".
Ranjit.
--
Ranjit Mathew Email: rmathew AT gmail DOT com
Bangalore, INDIA. Web: http://ranjitmathew.tripod.com/