This is the mail archive of the java-patches@gcc.gnu.org mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Getting Mauve to work.

From: Tom Tromey <tromey at redhat dot com>
To: Michael Koch <konqueror at gmx dot de>
Cc: Mark Wielaard <mark at klomp dot org>, java-patches at gcc dot gnu dot org
Date: 09 Jun 2003 10:09:17 -0600
Subject: Re: Getting Mauve to work.
References: <200306081248.18983.konqueror@gmx.de><200306081710.01737.konqueror@gmx.de><1055145587.779.1194.camel@elsschot><200306091023.36584.konqueror@gmx.de>
Reply-to: tromey at redhat dot com

Michael> Isnt mauve supposed to be correctly configured by libgcj
Michael> testsuite ?

Yes.  It works fine for me, either using MAUVEDIR or with a symlink
in the libgcj source tree.

You could add some "verbose" statements to mauve.exp to try to figure
out what is going wrong.  Did you do "make install"?  We've had bugs
in the past where not installing causes test suite failures of one
kind or another -- these "shouldn't happen" but still manage to from
time to time.

You can run just the Mauve part of the test suite like this:

    make RUNTESTFLAGS=mauve.exp

This should make it quicker to figure out what is going wrong...

Tom

References:
- Patch: java.io.PrintStream
  - From: Michael Koch
- Re: Patch: java.io.PrintStream
  - From: Michael Koch
- Re: Patch: java.io.PrintStream
  - From: Mark Wielaard
- Getting Mauve to work.
  - From: Michael Koch

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]