Testsuites and Test Results

[Gerald Pfeifer]

On Tue, 17 Jun 2003, Ranjit Mathew wrote:
> Ok, I'm attaching a modified patch below that makes this
> change to both install.texi and sourcebuild.texi.

Thanks!  I wrote a ChangeLog for the sourcebuild.texi part and committed
the following. (Sorry for not cooking the patch by myself yesterday.)

Gerald

2003-06-17  Ranjit Mathew  <rmathew@hotmail.com>
            Gerald Pfeifer  <pfeifer@dbai.tuwien.ac.at>

	* doc/sourcebuild.texi (libgcj Tests): Simplify instructions on how
	to run Java runtime tests separately.

Index: doc/sourcebuild.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/sourcebuild.texi,v
retrieving revision 1.23
diff -u -3 -p -r1.23 sourcebuild.texi
--- doc/sourcebuild.texi	15 Jun 2003 14:56:30 -0000	1.23
+++ doc/sourcebuild.texi	17 Jun 2003 18:58:49 -0000
@@ -944,9 +944,9 @@ test cases and magic comments more.
 @node libgcj Tests
 @subsection The Java library test suites.

-Runtime tests are executed via @samp{make check} from the @samp{testsuite}
-directory of the libjava hierarchy in the build tree.  Additional runtime
-tests can be checked into this testsuite.
+Runtime tests are executed via @samp{make check} in the
+@file{@var{target}/libjava/testsuite} directory in the build
+tree.  Additional runtime tests can be checked into this testsuite.

 Regression testing of the core packages in libgcj is also covered by the
 Mauve test suite.  The @uref{http://sources.redhat.com/mauve/,,Mauve Project}