mirror of
https://git.linuxfromscratch.org/lfs.git
synced 2025-07-05 11:59:51 +01:00
PDF fixes in chapter05
git-svn-id: http://svn.linuxfromscratch.org/LFS/branches/6.1/BOOK@4936 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
parent
b750f7c235
commit
0b5096ca63
@ -68,6 +68,8 @@ possibility:</para>
|
|||||||
|
|
||||||
<screen><userinput>rm -f /tools/lib/gcc/*/*/include/{pthread.h,bits/sigthread.h}</userinput></screen>
|
<screen><userinput>rm -f /tools/lib/gcc/*/*/include/{pthread.h,bits/sigthread.h}</userinput></screen>
|
||||||
|
|
||||||
|
<beginpage/>
|
||||||
|
|
||||||
<caution><para>At this point, it is imperative to stop and ensure that
|
<caution><para>At this point, it is imperative to stop and ensure that
|
||||||
the basic functions (compiling and linking) of the new toolchain are
|
the basic functions (compiling and linking) of the new toolchain are
|
||||||
working as expected. To perform a sanity check, run the following
|
working as expected. To perform a sanity check, run the following
|
||||||
|
@ -54,8 +54,9 @@ instructions be followed exactly as given above.</para>
|
|||||||
|
|
||||||
<para>To test the results, issue: <userinput>make
|
<para>To test the results, issue: <userinput>make
|
||||||
RUN_EXPENSIVE_TESTS=yes check</userinput>. The
|
RUN_EXPENSIVE_TESTS=yes check</userinput>. The
|
||||||
<parameter>RUN_EXPENSIVE_TESTS=yes</parameter> parameter tells the
|
<parameter condition="html">RUN_EXPENSIVE_TESTS=yes</parameter>
|
||||||
test suite to run several additional tests that are considered
|
<parameter condition="pdf">RUN_EXPENSIVE_ TESTS=yes</parameter>
|
||||||
|
parameter tells the test suite to run several additional tests that are considered
|
||||||
relatively expensive (in terms of CPU power and memory usage) on some
|
relatively expensive (in terms of CPU power and memory usage) on some
|
||||||
platforms, but generally are not a problem on Linux.</para>
|
platforms, but generally are not a problem on Linux.</para>
|
||||||
|
|
||||||
|
@ -82,6 +82,8 @@ scripts, which are not needed.</para></listitem>
|
|||||||
|
|
||||||
<para>The source directories of both Tcl and Expect can now be removed.</para>
|
<para>The source directories of both Tcl and Expect can now be removed.</para>
|
||||||
|
|
||||||
|
<beginpage/>
|
||||||
|
|
||||||
</sect2>
|
</sect2>
|
||||||
|
|
||||||
<sect2 id="contents-expect" role="content"><title>Contents of Expect</title>
|
<sect2 id="contents-expect" role="content"><title>Contents of Expect</title>
|
||||||
|
@ -84,6 +84,8 @@ tarball.</para></listitem>
|
|||||||
|
|
||||||
<screen><userinput>make bootstrap</userinput></screen>
|
<screen><userinput>make bootstrap</userinput></screen>
|
||||||
|
|
||||||
|
<beginpage/>
|
||||||
|
|
||||||
<para>The meaning of the make parameters:</para>
|
<para>The meaning of the make parameters:</para>
|
||||||
|
|
||||||
<variablelist>
|
<variablelist>
|
||||||
|
@ -164,6 +164,8 @@ target now because the compiler being used to compile this GCC was
|
|||||||
built from the exact same version of the GCC sources used
|
built from the exact same version of the GCC sources used
|
||||||
earlier.</para>
|
earlier.</para>
|
||||||
|
|
||||||
|
<beginpage/>
|
||||||
|
|
||||||
<para>Compilation is now complete. As previously mentioned, running
|
<para>Compilation is now complete. As previously mentioned, running
|
||||||
the test suites for the temporary tools compiled in this chapter is
|
the test suites for the temporary tools compiled in this chapter is
|
||||||
not mandatory. To run the GCC test suite anyway, use the following
|
not mandatory. To run the GCC test suite anyway, use the following
|
||||||
|
@ -78,7 +78,7 @@ for 2.6.x Linux kernels.</para></listitem>
|
|||||||
<term><parameter>--with-binutils=/tools/bin</parameter></term>
|
<term><parameter>--with-binutils=/tools/bin</parameter></term>
|
||||||
<listitem><para>While not required, this switch ensures that there are
|
<listitem><para>While not required, this switch ensures that there are
|
||||||
no errors pertaining to which Binutils programs get used during the
|
no errors pertaining to which Binutils programs get used during the
|
||||||
Glibc build.</para></listitem>
|
Glibc build.</para><beginpage/></listitem>
|
||||||
</varlistentry>
|
</varlistentry>
|
||||||
|
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
@ -152,6 +152,8 @@ off and continue. This stop-start sequence can be circumvented by
|
|||||||
issuing a <command>make -k check</command> command. If using this option, be sure to log the
|
issuing a <command>make -k check</command> command. If using this option, be sure to log the
|
||||||
output so that the log file can be examined for failures later.</para>
|
output so that the log file can be examined for failures later.</para>
|
||||||
|
|
||||||
|
<beginpage/>
|
||||||
|
|
||||||
<para>The install stage of Glibc will issue a harmless warning at the
|
<para>The install stage of Glibc will issue a harmless warning at the
|
||||||
end about the absence of <filename>/tools/etc/ld.so.conf</filename>.
|
end about the absence of <filename>/tools/etc/ld.so.conf</filename>.
|
||||||
Prevent this warning with:</para>
|
Prevent this warning with:</para>
|
||||||
|
@ -70,6 +70,8 @@ will need its internal headers.</para></warning>
|
|||||||
|
|
||||||
<screen><userinput>ln -s tclsh8.4 /tools/bin/tclsh</userinput></screen>
|
<screen><userinput>ln -s tclsh8.4 /tools/bin/tclsh</userinput></screen>
|
||||||
|
|
||||||
|
<beginpage/>
|
||||||
|
|
||||||
</sect2>
|
</sect2>
|
||||||
|
|
||||||
<sect2 id="contents-tcl" role="content"><title>Contents of Tcl</title>
|
<sect2 id="contents-tcl" role="content"><title>Contents of Tcl</title>
|
||||||
|
@ -80,6 +80,8 @@ might not show up until near the end of the build of an entire
|
|||||||
distribution. A test suite failure will usually alert this error
|
distribution. A test suite failure will usually alert this error
|
||||||
before too much additional work is performed.</para>
|
before too much additional work is performed.</para>
|
||||||
|
|
||||||
|
<beginpage/>
|
||||||
|
|
||||||
<para>Binutils installs its assembler and linker in two locations,
|
<para>Binutils installs its assembler and linker in two locations,
|
||||||
<filename class="directory">/tools/bin</filename> and <filename
|
<filename class="directory">/tools/bin</filename> and <filename
|
||||||
class="directory">/tools/$TARGET_TRIPLET/bin</filename>. The tools in
|
class="directory">/tools/$TARGET_TRIPLET/bin</filename>. The tools in
|
||||||
@ -167,6 +169,8 @@ the <xref linkend="chapter-temporary-tools"/> packages all build
|
|||||||
against the new Glibc in <filename
|
against the new Glibc in <filename
|
||||||
class="directory">/tools</filename>.</para>
|
class="directory">/tools</filename>.</para>
|
||||||
|
|
||||||
|
<beginpage/>
|
||||||
|
|
||||||
<para>Upon entering the chroot environment in <xref
|
<para>Upon entering the chroot environment in <xref
|
||||||
linkend="chapter-building-system"/>, the first major package to be
|
linkend="chapter-building-system"/>, the first major package to be
|
||||||
installed is Glibc, due to its self-sufficient nature mentioned above.
|
installed is Glibc, due to its self-sufficient nature mentioned above.
|
||||||
|
Loading…
Reference in New Issue
Block a user