diff options
| author | Pierre Labastie <pieere@linuxfromscratch.org> | 2020-06-18 10:00:48 +0000 |
|---|---|---|
| committer | Pierre Labastie <pieere@linuxfromscratch.org> | 2020-06-18 10:00:48 +0000 |
| commit | c3471cf4631eadcf3596f010305b079e61578356 (patch) | |
| tree | 0931029e35a80a983c8bc42fe5db77ad17e411d6 /part3intro | |
| parent | 80f8c024375dff45a2ddb3f7c9b49c9fc3c03ec4 (diff) | |
Fix several typos in toolchaintechnotes
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@11955 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'part3intro')
| -rw-r--r-- | part3intro/toolchaintechnotes.xml | 13 |
1 files changed, 7 insertions, 6 deletions
diff --git a/part3intro/toolchaintechnotes.xml b/part3intro/toolchaintechnotes.xml index 494666abc..221db039e 100644 --- a/part3intro/toolchaintechnotes.xml +++ b/part3intro/toolchaintechnotes.xml @@ -65,10 +65,11 @@ </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 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> <informaltable align="center"> @@ -88,7 +89,7 @@ <entry>build cross-compiler cc1 using ccA on machine A</entry> </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> </row> <row> @@ -215,9 +216,9 @@ instructions not available in the assembler instruction set. This internal library is named libgcc, and must be linked to the glibc library to be fully functional! Furthermore, the standard library for - C++ (libstdc++) also needs being linked to glibc. The solution - to this chicken and egg problem is to first build a degraded cc1 based libgcc, - lacking some fuctionalities such as threads and exception handling, then + C++ (libstdc++) also needs being linked to glibc. The solution to this + chicken and egg problem is to first build a degraded cc1 based libgcc, + lacking some functionalities such as threads and exception handling, then build glibc using this degraded compiler (glibc itself is not degraded), then build libstdc++. But this last library will lack the same functionalities as libgcc.</para> |