diff options
| -rw-r--r-- | gcc/ChangeLog | 10 | ||||
| -rw-r--r-- | gcc/doc/install.texi | 8 |
2 files changed, 18 insertions, 0 deletions
diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 9b1331f5f25..a149bc9674a 100644 --- 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 Richard Henderson <rth@redhat.com> * config/ia64/ia64.md: Use braced strings instead of quoted strings 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} |