Changeset c3471cf

Timestamp:

06/18/2020 10:00:48 AM (4 years ago)

Author:

Pierre Labastie <pieere@…>

Branches:

10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc

Children:

7772c15

Parents:

80f8c02

Message:

Fix several typos in toolchaintechnotes

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/trunk/BOOK@11955 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

File:

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

part3intro/toolchaintechnotes.xml

@@ -66 +66 @@
     </variablelist>
 
-    <para>As an example, let us imagine the following scenario: we may have a
+    <para>As an example, let us imagine the following scenario (sometimes
+    referred to as <quote>Canadian Cross</quote>): we may have a
     compiler on a slow machine only, let's call the machine A, and the compiler
     ccA. We may have also a fast machine (B), but with no compiler, and we may
-    want to produce code for a another slow machine (C). Then, to build a
+    want to produce code for another slow machine (C). To build a
     compiler for machine C, we would have three stages:</para>
 
@@ -89 +90 @@
           </row>
           <row>
-            <entry>2</entry><entry>A</entry><entry>B</entry><entry>B</entry>
+            <entry>2</entry><entry>A</entry><entry>B</entry><entry>C</entry>
             <entry>build cross-compiler cc2 using cc1 on machine A</entry>
           </row>
@@ -216 +217 @@
     internal library is named libgcc, and must be linked to the glibc
     library to be fully functional! Furthermore, the standard library for
-    C++ (libstdc++) also needs being linked to glibc. The solution
-    to this chicken and egg problem is to first build a degraded cc1 based libgcc,
-    lacking some fuctionalities such as threads and exception handling, then
+    C++ (libstdc++) also needs being linked to glibc. The solution to this
+    chicken and egg problem is to first build a degraded cc1 based libgcc,
+    lacking some functionalities such as threads and exception handling, then
     build glibc using this degraded compiler (glibc itself is not
     degraded), then build libstdc++. But this last library will lack the