install.texi (Testing): Mention two common DejaGnu warnings that can be ignored.

	* doc/install.texi (Testing): Mention two common DejaGnu warnings
	that can be ignored.

	* doc/install.texi (Final install): Recommend to install into a
	"clean" target directory.

From-SVN: r53555

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 70453eb6932b2ca5834246dece274cbc0910cf15..bc680343ffb1eaf6414846d4bfa154a5698cf020 100644 (file)
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,13 @@
+2002-05-17  Kurt Wall <kwall@kurtwerks.com>
+
+       * doc/install.texi (Testing): Mention two common DejaGnu warnings
+       that can be ignored.
+
+2002-05-16  Gerald Pfeifer  <pfeifer@dbai.tuwien.ac.at>
+
+       * doc/install.texi (Final install): Recommend to install into a
+       "clean" target directory.
+
 2002-05-17  Andreas Schwab  <schwab@suse.de>
 
        * config/ia64/sysv4.h (DO_SELECT_SECTION): Factored out of

diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi
index a321824a070e6f1be24d89d2823b3b8008542128..d97a98eb8f6286b490fdde7e8e5719a61558e1c3 100644 (file)
--- a/gcc/doc/install.texi
+++ b/gcc/doc/install.texi
@@ -1152,6 +1152,11 @@ The testing process will try to test as many components in the GCC
 distribution as possible, including the C, C++, Objective-C and Fortran
 compilers as well as the C++ and Java runtime libraries.
 
+While running the testsuite, DejaGnu might emit messages resembling
+@samp{WARNING: Couldn't find the global config file.} or 
+@samp{WARNING: Couldn't find tool init file}.
+These messages are harmless and do not affect the validity of the tests.
+
 @section How can I run the test suite on selected tests?
 
 As a first possibility to cut down the number of tests that are run it is
@@ -1256,6 +1261,9 @@ Now that GCC has been built (and optionally tested), you can install it with
 cd @var{objdir}; make install
 @end example
 
+We strongly recommend to install into a target directory where there is
+no previous version of GCC present.
+
 That step completes the installation of GCC; user level binaries can
 be found in @file{@var{prefix}/bin} where @var{prefix} is the value you
 specified with the @option{--prefix} to configure (or @file{/usr/local}