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

Fix several typos in toolchaintechnotes

Browse Source 
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@11955 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Pierre Labastie 2020-06-18 10:00:48 +00:00
parent 80f8c02437
commit c3471cf463
1 changed files with 7 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
part3intro/toolchaintechnotes.xml
View File

@ -65,10 +65,11 @@
</variablelist> </variablelist>
<para>As an example, let us imagine the following scenario: we may have a <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 the 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 a another slow machine (C). Then, 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>
<informaltable align="center"> <informaltable align="center">
@ -88,7 +89,7 @@
<entry>build cross-compiler cc1 using ccA on machine A</entry> <entry>build cross-compiler cc1 using ccA on machine A</entry>
</row> </row>
<row> <row>
<entry>2</entry><entry>A</entry><entry>B</entry><entry>B</entry> <entry>2</entry><entry>A</entry><entry>B</entry><entry>C</entry>
<entry>build cross-compiler cc2 using cc1 on machine A</entry> <entry>build cross-compiler cc2 using cc1 on machine A</entry>
</row> </row>
<row> <row>
@ -215,9 +216,9 @@
instructions not available in the assembler instruction set. This instructions not available in the assembler instruction set. This
internal library is named libgcc, and must be linked to the glibc internal library is named libgcc, and must be linked to the glibc
library to be fully functional! Furthermore, the standard library for library to be fully functional! Furthermore, the standard library for
C++ (libstdc++) also needs being linked to glibc. The solution C++ (libstdc++) also needs being linked to glibc. The solution to this
to this chicken and egg problem is to first build a degraded cc1 based libgcc, chicken and egg problem is to first build a degraded cc1 based libgcc,
lacking some fuctionalities such as threads and exception handling, then lacking some functionalities such as threads and exception handling, then
build glibc using this degraded compiler (glibc itself is not build glibc using this degraded compiler (glibc itself is not
degraded), then build libstdc++. But this last library will lack the degraded), then build libstdc++. But this last library will lack the
same functionalities as libgcc.</para> same functionalities as libgcc.</para>