Dennis J Perkins wrote:
> I noticed that glibc is now built only once and that it is installed
> in /usr. Actually, into $CLFS/usr, but install_root=$CLFS is used here.
>
> Why is it built only once? CLFS-1.0.0rc4 builds it twice and runs make
> check is run on the second version. CLFS-2.0 doesn't check it.
>
clfs-2.0 does not have a toolchain to build, that is why glibc is built
only once. With clfs-2.0 you go right from building the cross-tools to
building the final system. There is no /tools to chroot/boot into to
build the final system. In 1.0 the first gcc that is built in
cross-tools gets installed to /tools and the second glibc is built in
the final system.
> I've been experimenting with building the cross toolchain in order to
> learn it and I've found that if I use --with-sysroot when building
> glibc, the second stage gcc can't find some of the header files unless
> glibc is installed into /usr. I'm not sure why yet.
>
GCC is looking for headers in ${SYSROOT}/usr/{,local/}include . So
installing glibc to anywhere else besides ${SYSROOT}/usr won't put the
headers in /usr/include. --with-local-prefix=/tools is used when
building the toolchain in clfs-1.0.
clfs-2.0 is a completely different beast then clfs-1.0. Although
clfs-1.0 and clfs-1.0 aim to generate a 100% identical system. They go
about it a completely different way.
_______________________________________________
Clfs-support mailing list
[email protected]
http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-support
