[Clfs-support] Errors in GCC Testsuite (§10.21)

[Mark Pokorny]

---------- Forwarded message ----------
From: Mark Pokorny <iridium193 at gmail.com>
Date: 2009/9/26
Subject: Errors in GCC Testsuite (§10.21)
To: CLFS Support <clfs-support at lists.cross-lfs.org>


Hi all, hope you're all well.

I have run into some problems compiling the final system for x86_64
multilib; specifically with GCC 4.4.1. I get some errors when running
the check. This section of the book says "A few unexpected failures
cannot always be avoided. The GCC developers are usually aware of
these issues, but have not resolved them yet." Assuming the test
failures I've come across are the ones outlined in the book, I
proceeded to attempt to install that package, but this stalls with a
segmentation fault. Obviously the errors I have in the testsuite are a
little more serious than those inferred by the book. Does anyone know
what the cause is and how to work around it?

…

------------

I have some more information on this issue. First of all, I forgot to
mention in my last e-mail that I was using the x86_64 Multilib branch of the
SVN 2009-09-22 book. Sorry about that.

Anyway, in order to find out where exactly the installation routine failed,
I installed GCC 4.4.1 to a separated directory using:

make DESTDIR=/tmp/package install

This proceeds fine with no segmentation fault. However, when I try to copy
these files across using 'cp' with the options '-pPv', the segmentation
fault occurs when trying to copy libgcc_s.so.1 into the /usr/lib64
directory. I remember having some problems with this file previously; when
the build order for util-linux-ng and e2fsprogs was changed. Could this be
related?

I am using my own bootscripts (based on Arch Linux), the 2.6.31.1 Linux
kernel and I also compiled nano into the toolchain during Chapter 6 using
the same options as vim.

Regards,

Mark.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.clfs.org/pipermail/clfs-support-clfs.org/attachments/20091003/cbbf4b51/attachment.html>