From 7e62bbc5065ed196872a223c6558b89d4f9bce6d Mon Sep 17 00:00:00 2001 From: Bruce Dubbs Date: Fri, 17 Sep 2021 21:43:15 -0500 Subject: Tweak toolchain technical notes wording --- part3intro/toolchaintechnotes.xml | 20 ++++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) (limited to 'part3intro/toolchaintechnotes.xml') diff --git a/part3intro/toolchaintechnotes.xml b/part3intro/toolchaintechnotes.xml index ed5afc03b..72e3ab703 100644 --- a/part3intro/toolchaintechnotes.xml +++ b/part3intro/toolchaintechnotes.xml @@ -38,9 +38,9 @@ About Cross-Compilation 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. + 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. Let us first define some terms used in this context: @@ -67,7 +67,7 @@ As an example, let us imagine the following scenario (sometimes referred to as Canadian Cross): 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 compiler for machine C, we would have three stages: @@ -141,7 +141,7 @@ cpu-vendor-kernel-os referred to as the machine triplet. An astute reader may wonder why a triplet 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 triplet remained. A simple way to determine your machine triplet is to run the config.guess @@ -156,9 +156,9 @@ linker ld that is part of binutils). The dynamic linker 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 ld-linux.so.2 (ld-linux-x86-64.so.2 for 64-bit systems). A + dynamic linker for a 32-bit Intel machine is ld-linux.so.2 and isld-linux-x86-64.so.2 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: readelf -l <name of binary> | grep interpreter and noting the @@ -167,7 +167,7 @@ tree. - In order to fake a cross compilation, the name of the host triplet + In order to fake a cross compilation in LFS, the name of the host triplet is slightly adjusted by changing the "vendor" field in the LFS_TGT variable. We also use the --with-sysroot option when building the cross linker and @@ -295,7 +295,7 @@ checking what linker to use... /mnt/lfs/tools/i686-lfs-linux-gnu/bin/ld--host parameter passed to its configure script; e.g. in our case, the compiler will be $LFS_TGT-gcc. 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 configure, check the contents of the config.make file in the