Changeset 3c4e129 for part3intro/toolchaintechnotes.xml

Timestamp:

09/29/2022 07:12:10 PM (6 months ago)

Author:

David Bryant <davidbryant@…>

Branches:

11.3, 11.3-rc1, multilib, trunk, xry111/arm64, xry111/clfs-ng, xry111/glibc-2.37, xry111/kcfg-revise, xry111/pip3, xry111/rust-wip-20221008

Children:

0665add

Parents:

891b48b

Message:

Make minor corrections to English idiom / style.

File:

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

part3intro/toolchaintechnotes.xml

@@ -147 +147 @@
     <note>
       <para>Almost all the build systems use names of the form
-      cpu-vendor-kernel-os, referred to as the machine triplet. The vendor
-      field is sometimes omitted. An astute
+      cpu-vendor-kernel-os, referred to as the machine triplet. (Sometimes,
+      the vendor field is omitted.) An astute
       reader may wonder why a <quote>triplet</quote> refers to a four component
       name. The reason is historical: initially, three component names were enough
@@ -161 +161 @@
       system it will be <emphasis>x86_64-pc-linux-gnu</emphasis>. On most
       Linux systems the even simpler <command>gcc -dumpmachine</command> command
-      will give you the similar information.</para>
+      will give you similar information.</para>
 
       <para>You should also be aware of the name of the platform's dynamic linker, often
@@ -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 as a part of pass 2 gcc.</para>
+    compiler. So we have to re-build libstdc++ twice later on: as a part of
+    gcc stage 2, and then again in the chroot environment (gcc stage 3).</para>
 
   </sect2>