From 891b48b84b1e82a26b22428c66c74a3d14b6bd3a Mon Sep 17 00:00:00 2001
From: Xi Ruoyao <xry111@xry111.site>
Date: Thu, 29 Sep 2022 20:08:56 +0800
Subject: [PATCH] toolchaintechnotes: update description about libstdc++

Since r11.0-r199, libstdc++ pass 2 is built as a part of gcc pass 2, not
in chroot.
---
 part3intro/toolchaintechnotes.xml | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/part3intro/toolchaintechnotes.xml b/part3intro/toolchaintechnotes.xml
index 6a2f0adbc..c36c18ea3 100644
--- a/part3intro/toolchaintechnotes.xml
+++ b/part3intro/toolchaintechnotes.xml
@@ -241,7 +241,7 @@
     would be able to build those libraries, but (1) the build system of
     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>
 
@@ -329,8 +329,8 @@ checking what linker to use... /mnt/lfs/tools/i686-lfs-linux-gnu/bin/ld</compute
     <para>At the end of <xref linkend="chapter-temporary-tools"/> the native
     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
     different from the build system. This is why
@@ -338,8 +338,8 @@ checking what linker to use... /mnt/lfs/tools/i686-lfs-linux-gnu/bin/ld</compute
     as one of the configuration options.</para>
 
     <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
     <xref linkend="chapter-building-system"/>, final versions of all the