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: Tom Tromey <tromey at redhat dot com>
- To: Ranjit Mathew <rmathew at gmail dot com>
- Cc: java-patches at gcc dot gnu dot org
- Date: 06 May 2004 05:28:46 -0600
- Subject: Re: Patch: Run JNI tests using interpreter
- References: <40996CDA.90204@redhat.com> <4099D2BB.7080007@gmail.com>
- Reply-to: tromey at redhat dot com
>>>>> "Ranjit" == Ranjit Mathew <rmathew@gmail.com> writes:
Ranjit> Only if the testsuite is used independently of a GCC
Ranjit> build would this $PATH based picking up of "gcj"
Ranjit> make sense.
This used to be a supported way of running the test suite -- Cygnus
releng did things this way. The idea was, you test the install tree,
not the build tree (IMO a smart thing to do if you're shipping a
binary install).
I don't know if anybody presently relies on this functionality. I
wouldn't be opposed to an error by default, with some simple way to
re-enable PATH searching. In fact I think an error by default is the
most sensible thing.
Tom