Changeset 543c94c
- Timestamp:
- 09/30/2022 09:10:06 AM (19 months ago)
- Branches:
- 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, bdubbs/gcc13, multilib, renodr/libudev-from-systemd, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- d11d449
- Parents:
- 77b46db
- git-author:
- Xi Ruoyao <xry111@…> (09/30/2022 09:03:08 AM)
- git-committer:
- Xi Ruoyao <xry111@…> (09/30/2022 09:10:06 AM)
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
general.ent
r77b46db r543c94c 124 124 <!ENTITY fstab "<filename>/etc/fstab</filename>"> 125 125 <!ENTITY boot-dir "<filename class='directory'>/boot</filename>"> 126 <!ENTITY ch-final "<xref linkend='chapter-building-system'/>"> 127 <!ENTITY ch-tmp-cross "<xref linkend='chapter-temporary-tools'/>"> 128 <!ENTITY ch-tmp-chroot "<xref linkend='chapter-chroot-temporary-tools'/>"> 126 129 127 130 <!ENTITY % packages-entities SYSTEM "packages.ent"> -
part3intro/toolchaintechnotes.xml
r77b46db r543c94c 257 257 gcc does not know that it is usable on pc, and (2) using it on pc 258 258 would create a risk of linking to the pc libraries, since cc-lfs is a native 259 compiler. So we have to re-build libstdc++ twice later on: as a part of 260 gcc stage 2, and then again in the chroot environment (gcc stage 3).</para> 259 compiler. So we have to re-build libstdc++ later as a part of 260 gcc stage 2.</para> 261 262 <para>In &ch-final; (or <quote>stage 3</quote>), all packages needed for 263 the LFS system are built. Even if a package is already installed into 264 the LFS system in a previous chapter, we still rebuild the package 265 unless we are completely sure it's unnecessary. The main reason for 266 rebuilding these packages is to settle them down: if we reinstall a LFS 267 package on a complete LFS system, the installed content of the package 268 should be same as the content of the same package installed in 269 &ch-final;. The temporary packages installed in &ch-tmp-cross; or 270 &ch-tmp-chroot; cannot satisify this expectation because some of them 271 are built without optional dependencies installed, and autoconf cannot 272 perform some feature checks in &ch-tmp-cross; because of cross 273 compilation, causing the temporary packages to lack optional features 274 or use suboptimal code routines. Additionally, a minor reason for 275 rebuilding the packages is allowing to run the testsuite.</para> 261 276 262 277 </sect2>
Note:
See TracChangeset
for help on using the changeset viewer.