Changeset 716db1f for part3intro/toolchaintechnotes.xml

Timestamp:

09/20/2021 07:37:34 AM (3 years ago)

Author:

Thomas Trepl (Moody) <thomas@…>

Branches:

multilib

Children:

60870bc

Parents:

e680022 (diff), 7e62bbc (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the (diff) links above to see all the changes relative to each parent.

Message:

Merge upstream

File:

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

part3intro/toolchaintechnotes.xml

@@ -39 +39 @@
 
     <para>Cross-compilation involves some concepts that deserve a section on
-    their own. Although this section may be omitted in a first reading, it
-    is strongly suggested to come back to it later in order to get a full
-    grasp of the build process.</para>
+    their own. Although this section may be omitted in a first reading, 
+    coming back to it later will be beneficial to your full understanding of 
+    the process.</para>
 
     <para>Let us first define some terms used in this context:</para>
@@ -68 +68 @@
     <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
+    compiler on a slow machine only, let's call it 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 another slow machine (C). To build a
@@ -142 +142 @@
       reader may wonder why a <quote>triplet</quote> refers to a four component
       name. The reason is history: initially, three component names were enough
-      to designate unambiguously a machine, but with new machines and systems
+      to designate a machine unambiguously, but with new machines and systems
       appearing, that proved insufficient. The word <quote>triplet</quote>
       remained. A simple way to determine your machine triplet is to run
@@ -157 +157 @@
       provided by Glibc finds and loads the shared libraries needed by a
       program, prepares the program to run, and then runs it. The name of the
-      dynamic linker for a 32-bit Intel machine will be <filename
-      class="libraryfile">ld-linux.so.2</filename> (<filename
-      class="libraryfile">ld-linux-x86-64.so.2</filename> for 64-bit systems). A
+      dynamic linker for a 32-bit Intel machine is <filename
+      class="libraryfile">ld-linux.so.2</filename> and is<filename
+      class="libraryfile">ld-linux-x86-64.so.2</filename> for 64-bit systems. A
       sure-fire way to determine the name of the dynamic linker is to inspect a
       random binary from the host system by running: <userinput>readelf -l
@@ -168 +168 @@
     </note>
 
-    <para>In order to fake a cross compilation, the name of the host triplet
+    <para>In order to fake a cross compilation in LFS, the name of the host triplet
     is slightly adjusted by changing the &quot;vendor&quot; field in the
     <envar>LFS_TGT</envar> variable. We also use the
@@ -212 +212 @@
     just a compiler, but also defines a standard library. In this book, the
     GNU C library, named glibc, is used. This library must
-    be compiled for the lfs machine, that is, using the cross compiler cc1. 
+    be compiled for the lfs machine, that is, using the cross compiler cc1.
     But the compiler itself uses an internal library implementing complex
     instructions not available in the assembler instruction set. This
@@ -296 +296 @@
     parameter passed to its configure script; e.g. in our case, the compiler
     will be <command>$LFS_TGT-gcc</command>. The binary tools and kernel
-    headers can be a bit more complicated. Therefore, take no risks and use
+    headers can be a bit more complicated. Therefore, we take no risks and use
     the available configure switches to enforce the correct selections. After
     the run of <command>configure</command>, check the contents of the
@@ -330 +330 @@
     libstdc++. Then 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 
+    core toolchain is self-contained and self-hosted. In
     <xref linkend="chapter-building-system"/>, final versions of all the
     packages needed for a fully functional system are built, tested and