Commit 9e80ada7 by Phil Edwards

install.texi (*-*-linux-gnu): Mention glibc requirements for recent libstdc++.

2003-02-04  Phil Edwards  <pme@gcc.gnu.org>

	* doc/install.texi (*-*-linux-gnu):  Mention glibc requirements
	for recent libstdc++.  Remove formatting cruft.

From-SVN: r62379
parent 79c758fb
2003-02-04 Phil Edwards <pme@gcc.gnu.org>
* doc/install.texi (*-*-linux-gnu): Mention glibc requirements
for recent libstdc++. Remove formatting cruft.
2003-02-04 Jakub Jelinek <jakub@redhat.com> 2003-02-04 Jakub Jelinek <jakub@redhat.com>
* dwarf2out.c (dwarf2out_finish): Add AT_comp_dir * dwarf2out.c (dwarf2out_finish): Add AT_comp_dir
......
...@@ -2278,18 +2278,15 @@ have a higher-quality port for this machine soon. ...@@ -2278,18 +2278,15 @@ have a higher-quality port for this machine soon.
@end html @end html
@heading @anchor{*-*-linux-gnu}*-*-linux-gnu @heading @anchor{*-*-linux-gnu}*-*-linux-gnu
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 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++}. 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 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. applied in the GCC source tree, fixes the compatibility problems.
@html
@end html
@html
<p>
@end html
Currently Glibc 2.2.3 (and older releases) and GCC 3.0 are out of sync 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 since the latest exception handling changes for GCC@. Compiling glibc
with GCC 3.0 will give a binary incompatible glibc and therefore cause with GCC 3.0 will give a binary incompatible glibc and therefore cause
......
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