install.texi (mips-*-*): Recommend binutils 2.18.

2008-01-28  David Daney  <ddaney@avtrex.com>

	* doc/install.texi (mips-*-*): Recommend binutils 2.18.

From-SVN: r131911

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index cd415a4facd90281f08a6b1e6b1b558e960b8647..46fabaad01615737af2166ddf7911a3bc2f78052 100644 (file)
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,7 @@
+2008-01-28  David Daney  <ddaney@avtrex.com>
+
+       * doc/install.texi (mips-*-*): Recommend binutils 2.18.
+
 2008-01-28  David Daney  <ddaney@avtrex.com>
 
        * doc/install.texi (--disable-libgcj-bc):  Reword documentation.

diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi
index 7fed569521113ea57b3f19033e9e3a52cf78f3aa..4cdc76da4e04e3fb1ad9aaf836898061c48d2b21 100644 (file)
--- a/gcc/doc/install.texi
+++ b/gcc/doc/install.texi
@@ -3643,8 +3643,8 @@ it sorts relocations for REL targets (o32, o64, EABI).  This can cause
 bad code to be generated for simple C++ programs.  Also the linker
 from GNU binutils versions prior to 2.17 has a bug which causes the
 runtime linker stubs in very large programs, like @file{libgcj.so}, to
-be incorrectly generated.  Binutils CVS snapshots and releases made
-after Nov. 9, 2006 are thought to be free from both of these problems.
+be incorrectly generated.  GNU Binutils 2.18 and later (and snapshots
+made after Nov. 9, 2006) should be free from both of these problems.
 
 @html
 <hr />