Changeset 891b48b for part3intro/toolchaintechnotes.xml

Timestamp:

09/29/2022 12:08:56 PM (19 months ago)

Author:

Xi Ruoyao <xry111@…>

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:

3c4e129

Parents:

de94423

Message:

toolchaintechnotes: update description about libstdc++

Since r11.0-r199, libstdc++ pass 2 is built as a part of gcc pass 2, not
in chroot.

File:

• part3intro/toolchaintechnotes.xml (modified) (3 diffs)

part3intro/toolchaintechnotes.xml

@@ -242 +242 @@
     gcc does not know that it is usable on pc, and (2) using it on pc
     would create a risk of linking to the pc libraries, since cc-lfs is a native
-    compiler. So we have to re-build libstdc++ later, in the chroot environment.</para>
+    compiler. So we have to re-build libstdc++ later as a part of pass 2 gcc.</para>
 
   </sect2>
@@ -330 +330 @@
     LFS compiler is installed. First binutils-pass2 is built,
     in the same <envar>DESTDIR</envar> directory as the other programs,
-    then the second pass of gcc is constructed, omitting libstdc++
-    and other non-critical libraries.  Due to some weird logic in gcc's
+    then the second pass of gcc is constructed, omitting some
+    non-critical libraries.  Due to some weird logic in gcc's
     configure script, <envar>CC_FOR_TARGET</envar> ends up as
     <command>cc</command> when the host is the same as the target, but
@@ -339 +339 @@
 
     <para>Upon entering the chroot environment in <xref
-    linkend="chapter-chroot-temporary-tools"/>, the first task is to install
-    libstdc++. Then temporary installations of programs needed for the proper
+    linkend="chapter-chroot-temporary-tools"/>,
+    the temporary installations of programs needed for the proper
     operation of the toolchain are performed. From this point onwards, the
     core toolchain is self-contained and self-hosted. In