* doc/sourcebuild.texi (libgcj Tests): Simplify instructions on how

	to run Java runtime tests separately.

git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@68103 138bc75d-0d04-0410-961f-82ee72b054a4

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 8e49db0..3202bf8 100644 (file)
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,9 @@
+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.
+
 2003-06-17  Kazu Hirata  <kazu@cs.umass.edu>
 
        * config/h8300/h8300-protos.h: Update a comment.

diff --git a/gcc/doc/sourcebuild.texi b/gcc/doc/sourcebuild.texi
index a079bce..3537f1c 100644 (file)
--- a/gcc/doc/sourcebuild.texi
+++ b/gcc/doc/sourcebuild.texi
@@ -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}