OpenE2K
/
gcc
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

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
This commit is contained in:
Phil Edwards 2003-02-04 16:27:20 +00:00
parent 79c758fbcf
commit 9e80ada7a7
2 changed files with 9 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
gcc/ChangeLog
View File

@ -1,3 +1,8 @@
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>
* dwarf2out.c (dwarf2out_finish): Add AT_comp_dir

11
gcc/doc/install.texi
View File

@ -2278,18 +2278,15 @@ have a higher-quality port for this machine soon.
@end html
@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
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.
@html
@end html
@html
<p>
@end html
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