Changeset 3369724 for chapter01/how.xml
- Timestamp:
- 06/09/2020 03:57:09 PM (4 years ago)
- Branches:
- 10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- b99b7d3
- Parents:
- ce335792
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter01/how.xml
rce335792 r3369724 45 45 <xref linkend="chapter-final-preps"/> carefully as it explains several 46 46 important issues you need be aware of before beginning to 47 work your way through <xref linkend="chapter- temporary-tools"/> and beyond.</para>47 work your way through <xref linkend="chapter-cross-tools"/> and beyond.</para> 48 48 49 <para><xref linkend="chapter-temporary-tools"/> explains the installation of 50 a number of packages that are needed to resolve circular 51 dependencies—for example, to compile a compiler, you need a compiler. 52 or to unpack the tar package, you need tar.</para> 49 <para><xref linkend="chapter-cross-tools"/>, explains the installation of 50 the initial tool chain, (binutils, gcc, and glibc) using cross compilation 51 techniques to isolate the new tools from the host system.</para> 53 52 54 <para><xref linkend="chapter-temporary-tools"/> also shows you how to 55 build a C cross-compiling toolchain as a first step, including binutils 56 and GCC. Cross-compiling is not absolutely needed since the machine we'll 57 run LFS on is the same as the one we build on, but it has the advantage 58 of clearly separating the already installed system and the future LFS one. 59 The next step is to build Glibc, the C library. Glibc will be compiled by 60 the toolchain programs built previously. Then, the missing bits for a 61 C++ cross-compiling toolchain will be built. It is then possible to build 62 packages that are needed to resolve circular dependencies in such a way 63 that the produced executables and libraries are completely independent 64 from the installed distribution.</para> 53 <para><xref linkend="chapter-temporary-tools"/> shows you how to 54 cross-compile basic utilities using the just built cross-toolchain.</para> 65 55 66 <para>The remainder of <xref linkend="chapter-temporary-tools"/> adds 67 the packages necessary to get a complete build environment. This is done 68 after running the <command>chroot</command> (change root) program to enter 69 a virtual environment and start a new shell whose root directory will be 70 set to the LFS partition. This is very similar to rebooting and instructing 71 the kernel to mount the LFS partition as the root partition. The system 72 does not actually reboot, but instead uses <command>chroot</command> 73 because creating a bootable system requires additional work which is not 74 ecessary just yet. The major advantage is that <quote>chrooting</quote> 75 allows to isolate the build process from the installed distribution, while 76 using the installed kernel.</para> 56 <para><xref linkend="chapter-chroot-temporary-tools"/> then enters a 57 "chroot" environment and uses the previously built tools to build 58 the additional tools needed to build and test the final system.</para> 77 59 78 60 <para>This effort to isolate the new system from the host distribution may
Note:
See TracChangeset
for help on using the changeset viewer.