Xi Ruoyao d6006ef769 relax host system requirements ... A requirement on Glibc is not needed at all. It's enough once $LFS_TGT-* is runnable. A test on Alpine (using musl as libc) has practically proved this. We'd raised binutils and GCC requirements mostly for Glibc. But now Glibc is cross compiled by our cross toolchain with latest GCC and binutils release, the host tools really does not matter. In the Glibc building process only two .c files are build with BUILD_CC (the C compiler from the host), and they are highly conservative (mostly unchanged for years). Binutils does not have too much requirement on host GCC & Binutils: there is even a Binutils commit in this week fixing a build failure with GCC-4.2! So the most strict limitation comes from GCC. GCC requires host GCC to support ISO C++ 11 so GCC >= 4.8 is needed. And both GCC-4.8 and latest GCC-11.2 claims a requirement for Binutils-2.12 (for x86_64) or 2.13.1 (for 32-bit x86), so we make minimal Binutils version 2.13.1. And, host bzip2 is never used now: the only .tar.bz2 files are elfutils and python docs. They are not decompressed before entering chroot.		2022-02-19 10:29:47 +08:00
..
binutils-pass1.xml	Revert "binutils: use -j1 for make install"	2022-02-04 17:55:05 +08:00
chapter05.xml	Slightly change the layout in part III, so that the preliminary material	2020-06-17 20:50:25 +00:00
gcc-pass1.xml	relax host system requirements	2022-02-19 10:29:47 +08:00
glibc.xml	move the ln note back to chap 5 glibc	2021-11-12 00:41:02 +08:00
introduction.xml	Slightly change the layout in part III, so that the preliminary material	2020-06-17 20:50:25 +00:00
libstdc++.xml	break very long line	2022-02-15 15:45:00 +08:00
linux-headers.xml	Remove spaces at end o lines - chapter05	2021-09-07 22:43:31 +02:00