* 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.


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

1 files changed, 8 insertions, 0 deletions

diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi
index 6dd7f4445fe..d3b8aea04e3 100644
--- a/gcc/doc/install.texi
+++ b/gcc/doc/install.texi
@@ -1160,6 +1160,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
@@ -1264,6 +1269,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}