Re: Patch: Run JNI tests using interpreter

[Bryce McKinlay <mckinlay at redhat dot com>]

Ranjit Mathew wrote:

> 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".
>  

Looking at libjava.exp, it does default to running bare "gcj" etc, but 
only if it cant find them in the build directory. I guess in theory it 
might be useful to be able run the testsuite against an installed gcj 
rather than the build gcj, however. Does anyone do this?

Regards

Bryce