Changeset 1ce39f2
- Timestamp:
- 09/15/2003 11:12:22 PM (21 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, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v5_0, v5_1, v5_1_1, 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:
- f5ae45a6
- Parents:
- 1e163254
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter01/how.xml
r1e163254 r1ce39f2 17 17 18 18 <para>Chapter 5 will then discuss the installation of a number of packages that 19 will form the basic development suite (or tool -set) which is used to build the19 will form the basic development suite (or toolset) which is used to build the 20 20 actual system in Chapter 6. Some of these packages are needed to resolve 21 21 circular dependencies. For example, to compile a compiler you need a … … 32 32 the toolchain will be dynamically linked against the newly built Glibc. The 33 33 remaining Chapter 5 packages are all built using this second pass toolchain and 34 dynamically linked against the new host -independent Glibc. When this is done,34 dynamically linked against the new host independent Glibc. When this is done, 35 35 the LFS installation process will no longer depend on the host distribution, 36 36 with the exception of the running kernel. This is known as <quote>self … … 46 46 Binutils and GCC, they will be compiled statically. This means that the 47 47 version of the C library on your host distribution will be embedded inside all 48 the binary programs you just compiled. This will cause problems for you down49 the road (they have been well documented). The host's Glibc is usually an 50 unknown quantity and can contain bugs or anything else we don't know about48 the binary programs you just compiled. This has the potential to cause 49 problems for you down the road. The host's Glibc is usually an unknown 50 quantity and might even contain bugs or anything else we don't know about 51 51 until it is too late. A well known issue is that statically linked binaries 52 compiled on a Glibc-2.2.x based system that then contain calls to the 53 <emphasis>getpwuid()</emphasis> function crash when run on a Glibc-2.3.x based 54 system. You are 55 about to build a Glibc-2.3.x based system. You do not want to build something 56 that is going to crash do you? Finally, the Glibc autoconf tests produce 57 different results depending on whether an existing Glibc is found on the host 58 distribution. This can lead to inconsistencies and encourages hacks and 59 workarounds. With all these things in mind, you can see that the extra effort 60 to compile Binutils and GCC twice is well worth it.</para> 52 compiled on a Glibc-2.2.x based system that contain calls to the getpwuid() 53 function crash when run on a glibc-2.3.x based system. Seeing as we are about 54 to build a Glibc-2.3.x based system, we need to shield ourselves from problems 55 of this nature. The procedure employed in Chapter 5 achieves this goal. With 56 all these things in mind, you can see that the extra effort to compile 57 Binutils and GCC twice is well worth it.</para> 61 58 62 59 <para>In Chapter 6 your real LFS system will be built. The chroot (change root)
Note:
See TracChangeset
for help on using the changeset viewer.