doc/install.texi: Mention contrib/download_prerequisites

Mention ./contrib/download_prerequisites on the "Downloading GCC" page.

	* doc/invoke.texi (Downloading GCC): Mention
	contrib/download_prerequisites script.

From-SVN: r227619

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index fb9bbb787dc351194726ca15c66add50591112e6..0e3886982668b8d150d389994f490be77124cca4 100644 (file)
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,8 @@
+2015-09-10  Markus Trippelsdorf  <markus@trippelsdorf.de>
+
+       * doc/invoke.texi (Downloading GCC): Mention
+       contrib/download_prerequisites script.
+
 2015-09-10  Jakub Jelinek  <jakub@redhat.com>
 
        PR c++/67523

diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi
index 24e7eed1380038fc6996572c489d6e9aabd8f106..8ba52a0b4070b3239580e41728032c53d80eb9c7 100644 (file)
--- a/gcc/doc/install.texi
+++ b/gcc/doc/install.texi
@@ -565,7 +565,10 @@ components of the binutils you intend to build alongside the compiler
 @file{opcodes}, @dots{}) to the directory containing the GCC sources.
 
 Likewise the GMP, MPFR and MPC libraries can be automatically built
-together with GCC.  Unpack the GMP, MPFR and/or MPC source
+together with GCC.  You may simply run the
+./contrib/download_prerequisites script in the GCC source directory
+to set up everythingu.
+Otherwise unpack the GMP, MPFR and/or MPC source
 distributions in the directory containing the GCC sources and rename
 their directories to @file{gmp}, @file{mpfr} and @file{mpc},
 respectively (or use symbolic links with the same name).