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 question !!excpt.
+of all the other tools, of course). See also question question 2.8.
1.6. Which tools should I use for ARM?
else. The existing makefiles do most of the work; only some few stub rules
must be written to get everything running.
+Most add-ons are tightly coupled to a specific GNU libc version. Please
+check that the add-ons work with the GNU libc. For example the crypt and
+linuxthreads add-ons have the same numbering scheme as the libc and will in
+general only work with the corresponding libc.
+
1.12. My XXX kernel emulates a floating-point coprocessor for me.
Should I enable --with-fp?
problem. But you nevertheless should use EGCS for other reasons
(see question 1.2).
+{GK} On some Linux distributions for PowerPC, you can see this when you have
+built gcc or egcs from the Web sources (gcc versions 2.95 or earlier), 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.
+
2.9. How can I compile gcc 2.7.2.1 from the gcc source code using
glibc 2.x?