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

Make minor corrections to English idiom / style.

Browse Source
This commit is contained in:
David Bryant 2022-09-29 14:12:10 -05:00
parent 891b48b84b
commit 3c4e129d8c
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
part3intro/toolchaintechnotes.xml
View File

@ -146,8 +146,8 @@
<note> <note>
<para>Almost all the build systems use names of the form <para>Almost all the build systems use names of the form
cpu-vendor-kernel-os, referred to as the machine triplet. The vendor cpu-vendor-kernel-os, referred to as the machine triplet. (Sometimes,
field is sometimes omitted. An astute the vendor field is omitted.) 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 historical: initially, three component names were enough name. The reason is historical: initially, three component names were enough
to designate a machine unambiguously, but as new machines and systems to designate a machine unambiguously, but as new machines and systems
@ -160,7 +160,7 @@
output will be <emphasis>i686-pc-linux-gnu</emphasis>. On a 64-bit output will be <emphasis>i686-pc-linux-gnu</emphasis>. On a 64-bit
system it will be <emphasis>x86_64-pc-linux-gnu</emphasis>. On most system it will be <emphasis>x86_64-pc-linux-gnu</emphasis>. On most
Linux systems the even simpler <command>gcc -dumpmachine</command> command 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 <para>You should also be aware of the name of the platform's dynamic linker, often
referred to as the dynamic loader (not to be confused with the standard referred to as the dynamic loader (not to be confused with the standard
@ -241,7 +241,8 @@
would be able to build those libraries, but (1) the build system of would be able to build those libraries, but (1) the build system of
gcc does not know that it is usable on pc, and (2) using it on pc 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 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> </sect2>