Ignore:
Timestamp:
06/18/2020 10:00:48 AM (18 months ago)
Author:
Pierre Labastie <pieere@…>
Branches:
10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, ml-11.0, multilib, trunk, xry111/git-transition, xry111/glibc-2.34, xry111/tester-nohack, xry111/usr-move
Children:
7772c15
Parents:
80f8c02
Message:

Fix several typos in toolchaintechnotes

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@11955 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

File:
1 edited

Legend:

Unmodified
Added
Removed
  • part3intro/toolchaintechnotes.xml

    r80f8c02 rc3471cf  
    6666    </variablelist>
    6767
    68     <para>As an example, let us imagine the following scenario: we may have a
     68    <para>As an example, let us imagine the following scenario (sometimes
     69    referred to as <quote>Canadian Cross</quote>): we may have a
    6970    compiler on a slow machine only, let's call the machine A, and the compiler
    7071    ccA. We may have also a fast machine (B), but with no compiler, and we may
    71     want to produce code for a another slow machine (C). Then, to build a
     72    want to produce code for another slow machine (C). To build a
    7273    compiler for machine C, we would have three stages:</para>
    7374
     
    8990          </row>
    9091          <row>
    91             <entry>2</entry><entry>A</entry><entry>B</entry><entry>B</entry>
     92            <entry>2</entry><entry>A</entry><entry>B</entry><entry>C</entry>
    9293            <entry>build cross-compiler cc2 using cc1 on machine A</entry>
    9394          </row>
     
    216217    internal library is named libgcc, and must be linked to the glibc
    217218    library to be fully functional! Furthermore, the standard library for
    218     C++ (libstdc++) also needs being linked to glibc. The solution
    219     to this chicken and egg problem is to first build a degraded cc1 based libgcc,
    220     lacking some fuctionalities such as threads and exception handling, then
     219    C++ (libstdc++) also needs being linked to glibc. The solution to this
     220    chicken and egg problem is to first build a degraded cc1 based libgcc,
     221    lacking some functionalities such as threads and exception handling, then
    221222    build glibc using this degraded compiler (glibc itself is not
    222223    degraded), then build libstdc++. But this last library will lack the
Note: See TracChangeset for help on using the changeset viewer.