Changeset f8e4cf6


Ignore:
Timestamp:
10/31/2022 11:30:09 PM (18 months ago)
Author:
Thomas Trepl (Moody) <thomas@…>
Branches:
multilib
Children:
8c586d2
Parents:
1a76da0 (diff), 61f8251 (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the (diff) links above to see all the changes relative to each parent.
Message:

Automatic merge of trunk into multilib

File:
1 edited

Legend:

Unmodified
Added
Removed
  • part3intro/toolchaintechnotes.xml

    r1a76da0 rf8e4cf6  
    254254    functionality of libgcc.</para>
    255255
    256     <para>The upshot of the preceding
    257     paragraph is that cc1 is unable to build a fully functional libstdc++, but
    258     this is the only compiler available for building the C/C++ libraries
     256    <para>The upshot of the preceding paragraph is that cc1 is unable to
     257    build a fully functional libstdc++ with the degraded libgcc, but cc1
     258    is the only compiler available for building the C/C++ libraries
    259259    during stage 2. Of course, the compiler built by stage 2, cc-lfs,
    260260    would be able to build those libraries, but:</para>
     
    279279    </itemizedlist>
    280280
    281     <para>So we have to re-build libstdc++ later as a part of gcc stage 2.</para>
     281    <para>So when we build gcc stage 2, we instruct the building system to
     282    rebuild libgcc and libstdc++ with cc1, but link libstdc++ to the newly
     283    rebuilt libgcc instead of the degraded build.  Then the rebuilt
     284    libstdc++ will be fully functional.</para>
    282285
    283286    <para>In &ch-final; (or <quote>stage 3</quote>), all the packages needed for
Note: See TracChangeset for help on using the changeset viewer.