diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 9c1b245aee8c2e82d0edc5c36972b8cf41b1a7ce..a23c7c605d4239c58631c7b9958a50616adddcdd 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,8 @@
+2003-11-19  Gerald Pfeifer  <gp@suse.de>
+
+	* doc/install.texi (Specific): Remove information on old versions
+	of glibc versus old versions of GCC.
+
 2003-11-19  Richard SAndiford  <rsandifo@redhat.com>
 
 	* emit-rtl.c (gen_lowpart): Don't force MEMs into a register unless
diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi
index a62b9291a03ce0a9ef840347d8df2526d6108222..ac8ddfc02680410806f17878a62380d17d740130 100644
--- a/gcc/doc/install.texi
+++ b/gcc/doc/install.texi
@@ -2641,20 +2641,6 @@ Versions of libstdc++-v3 starting with 3.2.1 require bugfixes present
 in glibc 2.2.5 and later.  More information is available in the
 libstdc++-v3 documentation.
 
-If you use glibc 2.2 (or 2.1.9x), GCC 2.95.2 won't install
-out-of-the-box.  You'll get compile errors while building @samp{libstdc++}.
-The patch @uref{glibc-2.2.patch,,glibc-2.2.patch}, that is to be
-applied in the GCC source tree, fixes the compatibility problems.
-
-Currently Glibc 2.2.3 (and older releases) and GCC 3.0 are out of sync
-since the latest exception handling changes for GCC@.  Compiling glibc
-with GCC 3.0 will give a binary incompatible glibc and therefore cause
-lots of problems and might make your system completely unusable.  This
-will definitely need fixes in glibc but might also need fixes in GCC@.  We
-strongly advise to wait for glibc 2.2.4 and to read the release notes of
-glibc 2.2.4 whether patches for GCC 3.0 are needed.  You can use glibc
-2.2.3 with GCC 3.0, just do not try to recompile it.
-
 @html
 <hr />
 @end html