[Clfs-dev] CLFS Alpha - Version GIT-20130206-ALPHA
Karin WIllers
karin at visti.de
Sat Feb 9 03:06:53 PST 2013
Hello,
following the book, I encountered some problems:
vii. Errata
-----------
Following the given link:
http://trac.cross-lfs.org/clfs/errata/git/
the page displays the following:
Error: Not Found
No handler matched request to /clfs/errata/git
Is that normal?
5.8. GMP-5.0.5
--------------
On my machine (rather fresh Ubuntu 12.04 32-bit) the build resulted
in the following error:
configure error: checking C++ compiler g++ -fexceptions ... no
GMP.5.05 requires gcc with c++ support. 'version-check.sh' from
chapter "iv. Host System Requirements" could/should check for g++.
Something like
g++ --version | head -n1
should be added to the checking script
5.14. EGLIBC-2.15 Headers
-------------------------
EGLIBC requires autoconf and msgfmt. The commands
msgfmt --version | head -n1 and
autoconf --version | head -n1
could be added to the 'version-check.sh' script to test for that
at begin of the whole build procedure.
5.14. EGLIBC-2.15 Headers
-------------------------
In the current version, configure terminates with the error message:
checking sysdep dirs... configure: error: The alpha is not supported.
This comes from the fact that the EGLIBC Ports package is not added to
the EGLIBC source tree, as done in the other architectures I looked at.
Adding the first three commands from 5.15. EGLIBC-2.15 (MIPS Version):
tar -jxvf ../eglibc-ports-2.15-r21467.tar.xz
cp -v Makeconfig{,.orig}
sed -e 's/-lgcc_eh//g' Makeconfig.orig > Makeconfig
fixes that.
After that, configure terminates with the error message:
configure: error: linker with -z relro support required
I have two observations/questions:
First, why is the normal gcc (i684 host) used for this test?
Shouldn't be that the Alpha gcc (ok, chicken-egg-problem here ...)?
Second, other architectures build Cross GCC-4.6.3 - Static before
building EGLIBC, while on Alpha the order is
5.13. Cross Binutils-2.23
5.14. EGLIBC-2.15 Headers
5.15. Cross GCC-4.6.3 - Static
5.16. EGLIBC-2.15
Is there a specific reason for that?
On the other hand, when I build Cross GCC-4.6.3 - Static before EGLIBC,
the build stops with the following error:
In file included from ../../../gcc-4.6.3/libgcc/../gcc/unwind-dw2.c:333:0:
../../../gcc-4.6.3/libgcc/../gcc/config/alpha/linux-unwind.h:28:20: fatal
error: signal.h: No such file or directory
I'll look into the missing signal.h thing first, since my assumption
is that Cross GCC-4.6.3 - Static should be before EGLIBC.
Greetings, Karin
More information about the Clfs-dev
mailing list