Making the testsuite work for Mauve without installing

[Mark Wielaard]

Hi,

On Tue, 2002-04-30 at 22:45, Anthony Green wrote:
> On Tue, 2002-04-30 at 12:42, Mark Wielaard wrote:
> > 2002-04-30  Mark Wielaard  <mark@klomp.org>
> > 
> >         * lib/libjava.exp (libjava_init): Always use the just created
> >         libgcj.jar.
> 
> I think we should still support testing installed toolchains.  Won't
> this mess with that?

Yes most probably. The patch is intended to make sure the tests are
always run on the toolchain that was just build. But I admit that it
might be hacky since I don't yet know enough of DejaGNU/Tcl.

> I think at one point there were enough differences between testing an
> installed toolchain and one from the build directory that we just
> isolated all of the differences in a new spec file: libgcj-test.spec.in
> 
> Maybe we should go back to that.  It's sure easier than trying to figure
> out where the jar file and support libraries are in the expect scripts.

I will have to read up on spec files in that case.
The patch was intended as a quick fix to make sure that when someone
does a make -k check and MAUVEDIR is set the Mauve tests are correctly
run even when gcj is not yet installed (since make install takes up
extra time and space). I don't mind really learning DejaGNU, Tcl and
spec files to come up with a better test framework. But then I need some
examples of setups that people actually use since I don't have a clear
picture of how/why to test an installed toolchain inside the build dir.

Cheers,

Mark