diff options
Diffstat (limited to 'chapter01/how.xml')
| -rw-r--r-- | chapter01/how.xml | 48 |
1 files changed, 17 insertions, 31 deletions
diff --git a/chapter01/how.xml b/chapter01/how.xml index 3a8942dba..a690fb595 100644 --- a/chapter01/how.xml +++ b/chapter01/how.xml @@ -44,42 +44,28 @@ discusses the setup of an appropriate working environment. Please read <xref linkend="chapter-final-preps"/> carefully as it explains several important issues you need be aware of before beginning to - work your way through <xref linkend="chapter-temporary-tools"/> and beyond.</para> + work your way through <xref linkend="chapter-cross-tools"/> and beyond.</para> - <para><xref linkend="chapter-temporary-tools"/> explains the - installation of a number of packages that will form the basic - development suite (or toolchain) which is used to build the actual - system in <xref linkend="chapter-building-system"/>. Some of these - packages are needed to resolve circular dependencies—for example, - to compile a compiler, you need a compiler.</para> + <para><xref linkend="chapter-cross-tools"/>, explains the installation of + the initial tool chain, (binutils, gcc, and glibc) using cross compilation + techniques to isolate the new tools from the host system.</para> - <para><xref linkend="chapter-temporary-tools"/> also shows you how to - build a first pass of the toolchain, including Binutils and GCC (first pass - basically means these two core packages will be reinstalled). - The next step is to build Glibc, the C library. Glibc will be compiled by - the toolchain programs built in the first pass. Then, a second pass of the - toolchain will be built. This time, the toolchain will be dynamically linked - against the newly built Glibc. The remaining <xref - linkend="chapter-temporary-tools"/> packages are built using this second - pass toolchain. When this is done, the LFS installation process will no - longer depend on the host distribution, with the exception of the running - kernel. </para> + <para><xref linkend="chapter-temporary-tools"/> shows you how to + cross-compile basic utilities using the just built cross-toolchain.</para> + + <para><xref linkend="chapter-chroot-temporary-tools"/> then enters a + "chroot" environment and uses the previously built tools to build + the additional tools needed to build and test the final system.</para> <para>This effort to isolate the new system from the host distribution may - seem excessive. A full technical explanation as to why this is done is provided in - <xref linkend="ch-tools-toolchaintechnotes"/>.</para> + seem excessive. A full technical explanation as to why this is done is + provided in <xref linkend="ch-tools-toolchaintechnotes"/>.</para> - <para>In <xref linkend="chapter-building-system"/>, the full LFS system is - built. The <command>chroot</command> (change root) program is used to enter - a virtual environment and start a new shell whose root directory will be - set to the LFS partition. This is very similar to rebooting and instructing - the kernel to mount the LFS partition as the root partition. The system - does not actually reboot, but instead uses <command>chroot</command> because - creating a bootable system requires additional work which is not necessary - just yet. The major advantage is that <quote>chrooting</quote> allows you - to continue using the host system while LFS is being built. While waiting - for package compilations to complete, you can continue using your computer as - normal.</para> + <para>In <xref linkend="chapter-building-system"/>, The + full LFS system is built. Another advantage provided by the chroot + environment is that it allows you to continue using the host system + while LFS is being built. While waiting for package compilations to + complete, you can continue using your computer as normal.</para> <para>To finish the installation, the basic system configuration is set up in <xref linkend="chapter-config"/>, and the kernel and boot loader are set |