about summary refs log tree commit diff
path: root/FAQ
diff options
context:
space:
mode:
Diffstat (limited to 'FAQ')
-rw-r--r--FAQ37
1 files changed, 19 insertions, 18 deletions
diff --git a/FAQ b/FAQ
index 2342b0409f..2751f0d9c5 100644
--- a/FAQ
+++ b/FAQ
@@ -119,6 +119,7 @@ please let me know.
 2.35.	When recompiling GCC, I get compilation errors in libio.
 2.36.	Why shall glibc never get installed on GNU/Linux systems in
 /usr/local?
+2.37.	When recompiling GCC, I get compilation errors in libstdc++.
 
 3. Source and binary incompatibilities, and what to do about them
 
@@ -246,8 +247,7 @@ a local mirror first.
 
 You should always try to use the latest official release.  Older versions
 may not have all the features GNU libc requires.  The current releases of
-gcc (2.95 or newer) should work with the GNU C library (for powerpc see
-question 1.5; for ARM see question 1.6; for MIPS see question 1.20).
+gcc (3.2 or newer) should work with the GNU C library (for MIPS see question 1.20).
 
 Please note that gcc 2.95 and 2.95.x cannot compile glibc on Alpha due to
 problems in the complex float support.
@@ -281,19 +281,12 @@ them.
 
 1.5.	Which compiler should I use for powerpc?
 
-{GK} You want to use at least gcc 2.95 (together with the right versions
-of all the other tools, of course).  See also question 2.8.
+{} Removed.  Does not apply anymore.
 
 
 1.6.	Which tools should I use for ARM?
 
-{PB} You should use egcs 1.1 or a later version.  For ELF systems some
-changes are needed to the compiler; a patch against egcs-1.1.x can be found
-at:
-
-<ftp://ftp.netwinder.org/users/p/philb/egcs-1.1.1pre2-diff-981126>
-
-Binutils 2.10.1 or later is also required.
+{} Removed.  Does not apply anymore.
 
 
 1.7.	Do I need some more things to compile the GNU C Library?
@@ -499,9 +492,7 @@ test in the sources.
 
 There are some failures which are not directly related to the GNU libc:
 - Some compilers produce buggy code.  No compiler gets single precision
-  complex numbers correct on Alpha.  Otherwise, the egcs 1.1 release should be
-  ok; gcc 2.8.1 might cause some failures; gcc 2.7.2.x is so buggy that
-  explicit checks have been used so that you can't build with it.
+  complex numbers correct on Alpha.  Otherwise, gcc-3.2 should be ok.
 - The kernel might have bugs.  For example on Linux/Alpha 2.0.34 the
   floating point handling has quite a number of bugs and therefore most of
   the test cases in the math subdirectory will fail.  Linux 2.2 has
@@ -564,8 +555,8 @@ newer.
 
 1.20.	Which tools should I use for MIPS?
 
-{AJ} You should use the current development version of gcc 3.0 or newer from
-CVS.  gcc 2.95.x does not work correctly on mips-linux.
+{AJ} You should use the current development version of gcc 3.2 or newer from
+CVS.
 
 You need also recent binutils, anything before and including 2.11 will not
 work correctly.  Either try the Linux binutils 2.11.90.0.5 from HJ Lu or the
@@ -843,7 +834,7 @@ you got with your distribution.
 	glibc 2.x?
 
 {AJ} There's only correct support for glibc 2.0.x in gcc 2.7.2.3 or later.
-But you should get at least gcc 2.95.2.1 (or later versions) instead.
+But you should get at least gcc 2.95.3 (or later versions) anyway
 
 
 2.10.	The `gencat' utility cannot process the catalog sources which
@@ -1256,7 +1247,8 @@ repository.
 {BH} You are using g++ 2.95.2? After upgrading to glibc 2.2, you need to
 apply a patch to the include files in /usr/include/g++, because the fpos_t
 type has changed in glibc 2.2.  The patch is at
-http://clisp.cons.org/~haible/gccinclude-glibc-2.2-compat.diff
+
+  http://www.haible.de/bruno/gccinclude-glibc-2.2-compat.diff
 
 
 2.35.	When recompiling GCC, I get compilation errors in libio.
@@ -1279,6 +1271,15 @@ installation, use another directory as argument to --prefix.  If you like to
 install this glibc version as default version, overriding the existing one,
 use --prefix=/usr and everything will go in the right places.
 
+
+2.37.	When recompiling GCC, I get compilation errors in libstdc++.
+
+{BH} You are trying to recompile gcc 3.2?  You need to patch gcc 3.2,
+because some last minute changes were made in glibc 2.3 which were not
+known when gcc 3.2 was released.  The patch is at
+
+  http://www.haible.de/bruno/gcc-3.2-glibc-2.3-compat.diff
+
 
 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .