This is the mail archive of the libc-alpha@sources.redhat.com mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: glibc2.2 - Failed Assertions after upgrade


>>>>> Ulrich Drepper writes:

 > Andreas Jaeger <aj@suse.de> writes:
>> 2000-11-13  Andreas Jaeger  <aj@suse.de>
>> 
>> * configure.in: Require gcc 2.95 or newer.

 > Applied now.

And here's a patch for the FAQ and the manual.

Andreas

2000-11-16  Andreas Jaeger  <aj@suse.de>

	* manual/install.texi (Tools for Compilation): Update
	documentation for GCC 2.95.2.

============================================================
Index: manual/install.texi
--- manual/install.texi	2000/11/10 04:28:18	1.47
+++ manual/install.texi	2000/11/16 11:02:07
@@ -332,22 +332,17 @@
 versions have severe bugs or lack features.
 
 @item
-EGCS 1.1.1, 1.1 or 1.0.3, or GCC 2.8.1, 2.95 or newer
+GCC 2.95 or newer
 
 The GNU C library can only be compiled with the GNU C compiler family.
-As of the 2.1 release, EGCS 1.0.3 or higher is required.  GCC 2.8.1 can
-also be used (but see the FAQ for reasons why you might not want to).
-Earlier versions simply are too buggy.  As of this writing, GCC 2.95.2
-is the compiler we advise to use.
+As of the 2.2 release, GCC 2.95.2 or higher is required.  As of this
+writing, GCC 2.95.2 is the compiler we advise to use.
 
 You can use whatever compiler you like to compile programs that use GNU
 libc, but be aware that both GCC 2.7 and 2.8 have bugs in their
 floating-point support that may be triggered by the math library.
 
-On Alpha machines you need at least EGCS 1.1.1.  Earlier versions don't
-work reliably.
-
-For PPC you might need some patches even on top of the last EGCS version.
+For PPC you might need some patches even on top of the last GCC version.
 See the FAQ.
 
 @item
============================================================
Index: FAQ.in
--- FAQ.in	2000/11/08 20:15:31	1.115
+++ FAQ.in	2000/11/16 11:02:08
@@ -63,22 +63,9 @@
 
 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
-egcs (1.0.3 and 1.1.1) should work with the GNU C library (for powerpc see
+gcc (2.95 or newer) should work with the GNU C library (for powerpc see
 ?powerpc; for ARM see ?arm; for MIPS see ?mips).
 
-While the GNU CC should be able to compile glibc it is nevertheless adviced
-to use EGCS.  Comparing the sizes of glibc on Intel compiled with a recent
-EGCS and gcc 2.8.1 shows this:
-
-		  text    data     bss     dec     hex filename
-   egcs-2.93.10	862897   15944   12824  891665   d9b11 libc.so
-   gcc-2.8.1	959965   16468   12152  988585   f15a9 libc.so
-
-Make up your own decision.
-
-GNU CC versions 2.95 and above are derived from egcs, and they may do even
-better.
-
 Please note that gcc 2.95 and 2.95.x cannot compile glibc on Alpha due to
 problems in the complex float support.
 
@@ -193,11 +180,7 @@
 ??	The compiler hangs while building iconvdata modules.  What's
 	wrong?
 
-{ZW} This is a problem with old versions of GCC.  Initialization of large
-static arrays is very slow.  The compiler will eventually finish; give it
-time.
-
-The problem is fixed in egcs 1.1.
+{} Removed.  Does not apply anymore.
 
 ??	When I run `nm -u libc.so' on the produced library I still
 	find unresolved symbols.  Can this be ok?
@@ -643,8 +626,7 @@
 	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.8.1 or egcs 1.1 (or later versions)
-instead.
+But you should get at least gcc 2.95.2 (or later versions) instead.
 
 ??	The `gencat' utility cannot process the catalog sources which
 	were used on my Linux libc5 based system.  Why?

-- 
 Andreas Jaeger
  SuSE Labs aj@suse.de
   private aj@arthur.inka.de
    http://www.suse.de/~aj

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]