- 09/29/2022 12:08:56 PM (2 months ago)
- multilib, trunk, xry111/arm64, xry111/clfs-ng, xry111/pip3, xry111/rust-wip-20221008
- 1 edited
rde94423 r891b48b 242 242 gcc does not know that it is usable on pc, and (2) using it on pc 243 243 would create a risk of linking to the pc libraries, since cc-lfs is a native 244 compiler. So we have to re-build libstdc++ later , in the chroot environment.</para> 244 compiler. So we have to re-build libstdc++ later.</para> 245 245 246 246 </sect2> … … 330 330 LFS compiler is installed. First binutils-pass2 is built, 331 331 in the same <envar>DESTDIR</envar> directory as the other programs, 332 then the second pass of gcc is constructed, omitting libstdc++ 333 and othernon-critical libraries. Due to some weird logic in gcc's 332 then the second pass of gcc is constructed, omitting 333 non-critical libraries. Due to some weird logic in gcc's 334 334 configure script, <envar>CC_FOR_TARGET</envar> ends up as 335 335 <command>cc</command> when the host is the same as the target, but … … 339 339 340 340 <para>Upon entering the chroot environment in <xref 341 linkend="chapter-chroot-temporary-tools"/>, the first task is to install 342 libstdc++. Thentemporary installations of programs needed for the proper 341 linkend="chapter-chroot-temporary-tools"/>, 342 temporary installations of programs needed for the proper 343 343 operation of the toolchain are performed. From this point onwards, the 344 344 core toolchain is self-contained and self-hosted. In
Note: See TracChangeset for help on using the changeset viewer.