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

toolchaintechnotes: update description about libstdc++

Browse Source 
Since r11.0-r199, libstdc++ pass 2 is built as a part of gcc pass 2, not
in chroot.
This commit is contained in:
Xi Ruoyao 2022-09-29 20:08:56 +08:00
parent de94423625
commit 891b48b84b
No known key found for this signature in database
GPG Key ID: ACAAD20E19E710E3
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
part3intro/toolchaintechnotes.xml
View File

@ -241,7 +241,7 @@
would be able to build those libraries, but (1) the build system of would be able to build those libraries, but (1) the build system of
gcc does not know that it is usable on pc, and (2) using it on pc gcc does not know that it is usable on pc, and (2) using it on pc
would create a risk of linking to the pc libraries, since cc-lfs is a native would create a risk of linking to the pc libraries, since cc-lfs is a native
compiler. So we have to re-build libstdc++ later, in the chroot environment.</para> compiler. So we have to re-build libstdc++ later as a part of pass 2 gcc.</para>
</sect2> </sect2>
@ -329,8 +329,8 @@ checking what linker to use... /mnt/lfs/tools/i686-lfs-linux-gnu/bin/ld</compute
<para>At the end of <xref linkend="chapter-temporary-tools"/> the native <para>At the end of <xref linkend="chapter-temporary-tools"/> the native
LFS compiler is installed. First binutils-pass2 is built, LFS compiler is installed. First binutils-pass2 is built,
in the same <envar>DESTDIR</envar> directory as the other programs, in the same <envar>DESTDIR</envar> directory as the other programs,
then the second pass of gcc is constructed, omitting libstdc++ then the second pass of gcc is constructed, omitting some
and other non-critical libraries. Due to some weird logic in gcc's non-critical libraries. Due to some weird logic in gcc's
configure script, <envar>CC_FOR_TARGET</envar> ends up as configure script, <envar>CC_FOR_TARGET</envar> ends up as
<command>cc</command> when the host is the same as the target, but <command>cc</command> when the host is the same as the target, but
different from the build system. This is why different from the build system. This is why
@ -338,8 +338,8 @@ checking what linker to use... /mnt/lfs/tools/i686-lfs-linux-gnu/bin/ld</compute
as one of the configuration options.</para> as one of the configuration options.</para>
<para>Upon entering the chroot environment in <xref <para>Upon entering the chroot environment in <xref
linkend="chapter-chroot-temporary-tools"/>, the first task is to install linkend="chapter-chroot-temporary-tools"/>,
libstdc++. Then temporary installations of programs needed for the proper the temporary installations of programs needed for the proper
operation of the toolchain are performed. From this point onwards, the operation of the toolchain are performed. From this point onwards, the
core toolchain is self-contained and self-hosted. In core toolchain is self-contained and self-hosted. In
<xref linkend="chapter-building-system"/>, final versions of all the <xref linkend="chapter-building-system"/>, final versions of all the