gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-06-20 20:29:21 +01:00
Code Issues Packages Projects Releases Wiki Activity

Remove spaces at end o lines - part3intro

Browse Source
This commit is contained in:
Pierre Labastie 2021-09-07 22:47:52 +02:00
parent 2f72b72895
commit a665a20066
2 changed files with 3 additions and 3 deletions

2
part3intro/generalinstructions.xml
View File

@ -95,7 +95,7 @@
<listitem> <listitem>
<para>Using the <command>tar</command> program, extract the package <para>Using the <command>tar</command> program, extract the package
to be built. In <xref linkend="chapter-cross-tools"/> and to be built. In <xref linkend="chapter-cross-tools"/> and
<xref linkend="chapter-temporary-tools"/>, ensure you are <xref linkend="chapter-temporary-tools"/>, ensure you are
the <emphasis>lfs</emphasis> user when extracting the package.</para> the <emphasis>lfs</emphasis> user when extracting the package.</para>
</listitem> </listitem>
<listitem> <listitem>

4
part3intro/toolchaintechnotes.xml
View File

@ -211,7 +211,7 @@
<para>Now, there is more about cross-compiling: the C language is not <para>Now, there is more about cross-compiling: the C language is not
just a compiler, but also defines a standard library. In this book, the just a compiler, but also defines a standard library. In this book, the
GNU C library, named glibc, is used. This library must GNU C library, named glibc, is used. This library must
be compiled for the lfs machine, that is, using the cross compiler cc1. be compiled for the lfs machine, that is, using the cross compiler cc1.
But the compiler itself uses an internal library implementing complex But the compiler itself uses an internal library implementing complex
instructions not available in the assembler instruction set. This instructions not available in the assembler instruction set. This
internal library is named libgcc, and must be linked to the glibc internal library is named libgcc, and must be linked to the glibc
@ -329,7 +329,7 @@ checking what linker to use... /mnt/lfs/tools/i686-lfs-linux-gnu/bin/ld</compute
linkend="chapter-chroot-temporary-tools"/>, the first task is to install linkend="chapter-chroot-temporary-tools"/>, the first task is to install
libstdc++. Then temporary installations of programs needed for the proper libstdc++. Then 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
packages needed for a fully functional system are built, tested and packages needed for a fully functional system are built, tested and
installed.</para> installed.</para>