diff options
| author | Xi Ruoyao <xry111@xry111.site> | 2022-10-31 14:50:35 +0800 |
|---|---|---|
| committer | Xi Ruoyao <xry111@xry111.site> | 2022-10-31 14:50:35 +0800 |
| commit | 61f825108e4b153a4eb814f4dd290a65e1400b68 (patch) | |
| tree | 3a551cd310ca0636b385c3083f203faca6a90b36 /part3intro | |
| parent | decf315c6d9168528dfbcab3fd091dee768e2294 (diff) | |
toolchaintechnotes: reword the explanation about rebuild libstdc++ in gcc pass 2
Diffstat (limited to 'part3intro')
| -rw-r--r-- | part3intro/toolchaintechnotes.xml | 11 |
1 files changed, 7 insertions, 4 deletions
diff --git a/part3intro/toolchaintechnotes.xml b/part3intro/toolchaintechnotes.xml index 5698115cf..7401350d8 100644 --- a/part3intro/toolchaintechnotes.xml +++ b/part3intro/toolchaintechnotes.xml @@ -253,9 +253,9 @@ degraded), and also to build libstdc++. This last library will lack some of the 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> @@ -278,7 +278,10 @@ </listitem> </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 the LFS system are built. Even if a package has already been installed into |