gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-06-18 19:29:21 +01:00
Code Issues Packages Projects Releases Wiki Activity

Tweak toolchain technical notes wording

Browse Source
This commit is contained in:
Bruce Dubbs 2021-09-17 21:43:15 -05:00
parent 43b6ecdc1f
commit 7e62bbc506
1 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
part3intro/toolchaintechnotes.xml
View File

@ -38,9 +38,9 @@
<title>About Cross-Compilation</title> <title>About Cross-Compilation</title>
<para>Cross-compilation involves some concepts that deserve a section on <para>Cross-compilation involves some concepts that deserve a section on
their own. Although this section may be omitted in a first reading, it their own. Although this section may be omitted in a first reading,
is strongly suggested to come back to it later in order to get a full coming back to it later will be beneficial to your full understanding of
grasp of the build process.</para> the process.</para>
<para>Let us first define some terms used in this context:</para> <para>Let us first define some terms used in this context:</para>
@ -67,7 +67,7 @@
<para>As an example, let us imagine the following scenario (sometimes <para>As an example, let us imagine the following scenario (sometimes
referred to as <quote>Canadian Cross</quote>): we may have a 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 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 want to produce code for another slow machine (C). To build a
compiler for machine C, we would have three stages:</para> compiler for machine C, we would have three stages:</para>
@ -141,7 +141,7 @@
cpu-vendor-kernel-os referred to as the machine triplet. An astute cpu-vendor-kernel-os referred to as the machine triplet. An astute
reader may wonder why a <quote>triplet</quote> refers to a four component reader may wonder why a <quote>triplet</quote> refers to a four component
name. The reason is history: initially, three component names were enough 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> appearing, that proved insufficient. The word <quote>triplet</quote>
remained. A simple way to determine your machine triplet is to run remained. A simple way to determine your machine triplet is to run
the <command>config.guess</command> the <command>config.guess</command>
@ -156,9 +156,9 @@
linker <command>ld</command> that is part of binutils). The dynamic linker linker <command>ld</command> that is part of binutils). The dynamic linker
provided by Glibc finds and loads the shared libraries needed by a 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 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 dynamic linker for a 32-bit Intel machine is <filename
class="libraryfile">ld-linux.so.2</filename> (<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 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 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 random binary from the host system by running: <userinput>readelf -l
&lt;name of binary&gt; | grep interpreter</userinput> and noting the &lt;name of binary&gt; | grep interpreter</userinput> and noting the
@ -167,7 +167,7 @@
tree.</para> tree.</para>
</note> </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 is slightly adjusted by changing the &quot;vendor&quot; field in the
<envar>LFS_TGT</envar> variable. We also use the <envar>LFS_TGT</envar> variable. We also use the
<parameter>--with-sysroot</parameter> option when building the cross linker and <parameter>--with-sysroot</parameter> 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</compute
always use the compiler relating to the <parameter>--host</parameter> always use the compiler relating to the <parameter>--host</parameter>
parameter passed to its configure script; e.g. in our case, the compiler 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 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 available configure switches to enforce the correct selections. After
the run of <command>configure</command>, check the contents of the the run of <command>configure</command>, check the contents of the
<filename>config.make</filename> file in the <filename <filename>config.make</filename> file in the <filename