Changeset 61f8251

Timestamp:

10/31/2022 06:50:35 AM (18 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/update-glibc

Children:

3f43049, 98755ac, 9974e9b, f8e4cf6

Parents:

decf315

Message:

toolchaintechnotes: reword the explanation about rebuild libstdc++ in gcc pass 2

File:

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

part3intro/toolchaintechnotes.xml

@@ -254 +254 @@
     functionality of libgcc.</para>
 
-    <para>The upshot of the preceding
-    paragraph is that cc1 is unable to build a fully functional libstdc++, but
-    this is the only compiler available for building the C/C++ libraries
+    <para>The upshot of the preceding paragraph is that cc1 is unable to
+    build a fully functional libstdc++ with the degraded libgcc, but cc1
+    is the only compiler available for building the C/C++ libraries
     during stage 2. Of course, the compiler built by stage 2, cc-lfs,
     would be able to build those libraries, but:</para>
@@ -279 +279 @@
     </itemizedlist>
 
-    <para>So we have to re-build libstdc++ later as a part of gcc stage 2.</para>
+    <para>So when we build gcc stage 2, we instruct the building system to
+    rebuild libgcc and libstdc++ with cc1, but link libstdc++ to the newly
+    rebuilt libgcc instead of the degraded build.  Then the rebuilt
+    libstdc++ will be fully functional.</para>
 
     <para>In &ch-final; (or <quote>stage 3</quote>), all the packages needed for