This is the mail archive of the libc-alpha@sourceware.cygnus.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: glibc 2.1.2pre3


> From: Ulrich Drepper <drepper@cygnus.com>
> Date: 25 Aug 1999 15:06:56 -0700
> 
> I've uploaded the third prerelease for glibc 2.1.2 to
...
> So, test this version and send feedback to libc-alpha@sourceware.cygnus.com.

Works fine for me on ppc-linux.

However, the FAQ doesn't seem to be quite up-to-date; it's important
to have at least the warning about frame.o, because it can cause
people to update their glibc, have it pass 'make check', but then have
a system which won't boot.

It'd also be good to say that 2.95.1 is the preferred version for PPC,
because it's the very first version that will compile glibc without
any extra patches.

You might also like to put in a mention of 64-bit machines and gcc
2.95*---I'll leave that up to you.

-- 
Geoffrey Keating <geoffk@cygnus.com>

===File ~/patches/glibc-54.diff=============================
--- /usr/src/redhat/BUILD/glibc-2.1.2/FAQ.in	Fri Jul  9 11:15:30 1999
+++ FAQ.in	Sat Jul 31 11:53:37 1999
@@ -73,6 +73,9 @@
 
 Make up your own decision.
 
+GNU CC versions 2.95 and above are derived from egcs, and they may do even
+better.
+
 ??	When I try to compile glibc I get only error messages.
 	What's wrong?
 
@@ -103,16 +106,8 @@
 
 ??powerpc	Which compiler should I use for powerpc?
 
-{GK} You want to use egcs 1.1 or later (together with the right versions
-of all the other tools, of course).
-
-In fact, egcs 1.1 has a bug that causes linuxthreads to be
-miscompiled, resulting in segmentation faults when using condition
-variables.  There is a temporary patch at:
-
-<http://discus.anu.edu.au/~geoffk/egcs-3.diff>
-
-Later versions of egcs may fix this problem.
+{GK} You want to use at least gcc 2.95.1 (together with the right versions
+of all the other tools, of course).  See also question ?excpt.
 
 ??arm	Which tools should I use for ARM?
 
@@ -167,6 +162,9 @@
   <yann@plato.uni-paderborn.de> reports 22h48m on Atari TT030
   (Motorola 68030 @ 32 Mhz, 34 Mb memory)
 
+  A full build of the PowerPC library took 1h on a PowerPC 750@400Mhz w/
+  64MB of RAM, and about 9h on a 601@60Mhz w/ 72Mb. 
+
   If you have some more measurements let me know.
 
 ??	What version of the Linux kernel headers should be used?
@@ -568,7 +566,7 @@
 
 GROUP ( libc.so.6 libc_nonshared.a )
 
-??	When I run an executable on one system which I compiled on
+??excpt	When I run an executable on one system which I compiled on
 	another, I get dynamic linker errors.  Both systems have the same
 	version of glibc installed.  What's wrong?
 
@@ -598,6 +596,24 @@
 newer since we have explicitly add references to the functions causing the
 problem.  But you nevertheless should use EGCS for other reasons
 (see ?binsize).
+
+{GK} On some Linux distributions for PowerPC, you can see this when you have
+built gcc or egcs from the Web sources, then re-built glibc.  This happens
+because in these versions of gcc, exception handling is implemented using
+an older method; the people making the distributions are a little ahead
+of their time.
+
+A quick solution to this is to find the libgcc.a file that came with the
+distribution (it would have been installed under /usr/lib/gcc-lib), do 
+`ar x libgcc.a frame.o' to get the frame.o file out, and add a line saying
+`LDLIBS-c.so += frame.o' to the file `configparms' in the directory you're
+building in.  You can check you've got the right `frame.o' file by running
+`nm frame.o' and checking that it has the symbols defined that you're
+missing.
+
+This will let you build glibc with the C compiler.  The C++ compiler
+will still be binary incompatible with any C++ shared libraries that
+you got with your distribution.
 
 ??	How can I compile gcc 2.7.2.1 from the gcc source code using
 	glibc 2.x?
============================================================

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