Re: Mauve on Solaris 2.8

[Mark Wielaard <mark at klomp dot org>]

Hi,

On Thu, 2002-04-04 at 18:38, Andrew Haley wrote:
> It's been ages since I used Mauve.  I get this on 3.1 branch:
> 
> touch classes.stamp
> make[2]: Leaving directory `/export/scratch1/aph/gcc-3_1-branch/build/sparc-sun-solaris2.8/libjava/testsuite/mauve-build'
> ERROR: (DejaGnu) proc "bytecompile_file /export/scratch1/aph/gcc-3_1-branch/gcc/libjava/testsuite/libjava.mauve/DejaGNUTestHarness.java /export/scratch1/aph/gcc-3_1-branch/build/sparc-sun-solaris2.8/libjava/testsuite/mauve-build /export/scratch1/aph/mauve:/export/scratch1/aph/gcc-3_1-branch/build/sparc-sun-solaris2.8/libjava/testsuite/mauve-build" does not exist.
> The error code is NONE
> The info on the error is:
> no files matched glob pattern "/export/scratch1/aph/gcc-3_1-branch/gcc/libjava/testsuite/libjava.mauve/libjava.mauve*"
>     while executing
> "glob /export/scratch1/aph/gcc-3_1-branch/gcc/libjava/testsuite/libjava.mauve/libjava.mauve*"
>     invoked from within
> "catch "glob ${path}/${pattern}" tmp"
> 
>                 === libjava.mauve Summary ===
> 
> I've no idea what might be causing this.
> 
> I set MAUVEDIR to point to the top of the Mauve sourcedir, then do a
> "make check" in build/libjava.  Am I missing something?
> 
I remember that I had to do the aclocal; autoheader; automake; autoconf
in the toplevel mauvedir since since the configure from CVS didn't work
out of the box.

Then I do a make check-target-libgcj in my object dir (that runs all the
libgcj tests not just mauve). It should create a
${platform}/libjava/testsuite/mauve-build dir that you seem to have.

I am not sure what goes wrong.

Cheers,

Mark