From: Gerald Pfeifer Date: Fri, 17 May 2002 10:49:28 +0000 (+0000) Subject: install.texi (Testing): Mention two common DejaGnu warnings that can be ignored. X-Git-Tag: releases/gcc-3.1.1~341 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=b99b7ba8601d3418b78856e1cf21e0fc9f5d3fac;p=thirdparty%2Fgcc.git 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 70453eb6932b..bc680343ffb1 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,13 @@ +2002-05-17 Kurt Wall + + * doc/install.texi (Testing): Mention two common DejaGnu warnings + that can be ignored. + +2002-05-16 Gerald Pfeifer + + * doc/install.texi (Final install): Recommend to install into a + "clean" target directory. + 2002-05-17 Andreas Schwab * config/ia64/sysv4.h (DO_SELECT_SECTION): Factored out of diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi index a321824a070e..d97a98eb8f62 100644 --- 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}