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

Moving the notes on critical tests to a more conspicuous place.

Browse Source 
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3191 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Alex Gronenwoud 2004-01-28 22:10:21 +00:00
parent 3be4d973d4
commit 90afe40d90
3 changed files with 12 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
chapter06/binutils.xml
View File

@ -31,10 +31,6 @@ are able to resolve the issue. Please refer back to <xref linkend="ch-system-pro
and the <xref linkend="ch-system-MAKEDEV"/> section and perform the recommended steps and the <xref linkend="ch-system-MAKEDEV"/> section and perform the recommended steps
to fix the problem.</para> to fix the problem.</para>
<note><para>The test suite for Binutils in this section is considered
<emphasis>critical</emphasis>. Our advice is to not skip it under any
circumstances.</para> </note>
<para>This package is known to behave badly when you have changed its <para>This package is known to behave badly when you have changed its
default optimization flags (including the -march and -mcpu options). default optimization flags (including the -march and -mcpu options).
Therefore, if you have defined any environment variables that override Therefore, if you have defined any environment variables that override
@ -64,6 +60,10 @@ build for our own system, we don't need this target specific directory in
cross-compile (for example compiling a package on an Intel machine that cross-compile (for example compiling a package on an Intel machine that
generates code that can be executed on PowerPC machines).</para> generates code that can be executed on PowerPC machines).</para>
<important><para>The test suite for Binutils in this section is considered
<emphasis>critical</emphasis>. Our advice is to not skip it under any
circumstances.</para></important>
<para>Test the results:</para> <para>Test the results:</para>
<screen><userinput>make check</userinput></screen> <screen><userinput>make check</userinput></screen>

8
chapter06/gcc.xml
View File

@ -20,10 +20,6 @@ And for the GCC No-Fixincludes Patch:
<sect2> <sect2>
<title>Installation of GCC</title> <title>Installation of GCC</title>
<note><para>The test suite for GCC in this section is considered
<emphasis>critical</emphasis>. Our advice is to not skip it under any
circumstance.</para></note>
<para>This package is known to behave badly when you have changed its <para>This package is known to behave badly when you have changed its
default optimization flags (including the -march and -mcpu options). default optimization flags (including the -march and -mcpu options).
Therefore, if you have defined any environment variables that override Therefore, if you have defined any environment variables that override
@ -67,6 +63,10 @@ cd ../gcc-build</userinput></screen>
<screen><userinput>make</userinput></screen> <screen><userinput>make</userinput></screen>
<important><para>The test suite for GCC in this section is considered
<emphasis>critical</emphasis>. Our advice is to not skip it under any
circumstance.</para></important>
<para>Test the results, but don't stop at errors (you'll remember the few <para>Test the results, but don't stop at errors (you'll remember the few
known ones):</para> known ones):</para>

8
chapter06/glibc.xml
View File

@ -24,10 +24,6 @@ at <filename>/tools</filename>. We cannot adjust the specs and linker before
the Glibc install, because the Glibc autoconf tests would then give bogus the Glibc install, because the Glibc autoconf tests would then give bogus
results and thus defeat our goal of achieving a clean build.</para> results and thus defeat our goal of achieving a clean build.</para>
<note><para>The test suite for Glibc in this section is considered
<emphasis>critical</emphasis>. Our advice is to not skip it under any
circumstance.</para></note>
<para>Before starting to build Glibc, remember to unset any environment <para>Before starting to build Glibc, remember to unset any environment
variables that override the default optimization flags.</para> variables that override the default optimization flags.</para>
@ -67,6 +63,10 @@ kernel headers into <filename>/usr/include</filename>.</para></listitem>
<screen><userinput>make</userinput></screen> <screen><userinput>make</userinput></screen>
<important><para>The test suite for Glibc in this section is considered
<emphasis>critical</emphasis>. Our advice is to not skip it under any
circumstance.</para></important>
<para>Test the results:</para> <para>Test the results:</para>
<screen><userinput>make check</userinput></screen> <screen><userinput>make check</userinput></screen>