Commit 4550b19e by Gerald Pfeifer Committed by Gerald Pfeifer

install.texi (Specific): Remove information on old versions of glibc versus old versions of GCC.

	* doc/install.texi (Specific): Remove information on old versions
	of glibc versus old versions of GCC.

From-SVN: r73738
parent e9b926d1
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> 2003-11-19 Richard SAndiford <rsandifo@redhat.com>
* emit-rtl.c (gen_lowpart): Don't force MEMs into a register unless * emit-rtl.c (gen_lowpart): Don't force MEMs into a register unless
......
...@@ -2641,20 +2641,6 @@ Versions of libstdc++-v3 starting with 3.2.1 require bugfixes present ...@@ -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 in glibc 2.2.5 and later. More information is available in the
libstdc++-v3 documentation. 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 @html
<hr /> <hr />
@end html @end html
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment