gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-03-06 06:14:47 +00:00
Code Issues Packages Projects Releases Wiki Activity

Making the chapter 6 tests more obviously optional.

Browse Source 
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3234 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Alex Gronenwoud 2004-02-07 10:48:55 +00:00
parent c21999c677
commit 8a5f9064c4
21 changed files with 53 additions and 121 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
chapter06/autoconf.xml
View File

@ -23,15 +23,9 @@ can automatically configure source code.</para>
<screen><userinput>make</userinput></screen>
<para>This package has a test suite available which performs a number of
checks to ensure it will function correctly. It's worth noting that Autoconf
does not play a critical role in the overall operation of an LFS system. In
addition, the Autoconf test suite runs for quite a long period of time.
Accordingly, the running of the test suite here is not crucial. Should you
choose to run the Autoconf test suite, the following command will do
so:</para>
<screen><userinput>make check</userinput></screen>
<para>To have the results tested, issue:
<userinput>make check</userinput>.This takes a long time, about 2 SBUs,
and is strictly optional.</para>
<para>And install the package:</para>

12
chapter06/automake.xml
View File

@ -24,15 +24,9 @@ with Autoconf.</para>
<screen><userinput>make</userinput></screen>
<para>This package has a test suite available which performs a number of
checks to ensure it will function correctly. It's worth noting that Automake
does not play a critical role in the overall operation of an LFS system. In
addition, the Automake test suite runs for quite a long period of time.
Accordingly, the running of the test suite here is not crucial. Should you
choose to run the Automake test suite, the following command will do
so:</para>
<screen><userinput>make check</userinput></screen>
<para>To have the results tested, issue:
<userinput>make check</userinput>. This takes a long time, about 4 SBUs,
and is strictly optional.</para>
<para>Install the package:</para>

7
chapter06/bash.xml
View File

@ -29,11 +29,8 @@ patch:</para>
<screen><userinput>make</userinput></screen>
<para>This package has a test suite available which can perform a number of
checks to ensure it built correctly. Should you choose to run it, the
following command will do so:</para>
<screen><userinput>make tests</userinput></screen>
<para>To have the results tested, issue:
<userinput>make tests</userinput>.</para>
<para>Install the package:</para>

7
chapter06/bison.xml
View File

@ -28,11 +28,8 @@ the patch is backported from CVS:</para>
<screen><userinput>make</userinput></screen>
<para>This package has a test suite available which can perform a number of
checks to ensure it built correctly. Should you choose to run it, the
following command will do so (and takes a long time):</para>
<screen><userinput>make check</userinput></screen>
<para>To have the results tested, issue:
<userinput>make check</userinput>.</para>
<para>And install the package:</para>

9
chapter06/coreutils.xml
View File

@ -41,14 +41,13 @@ provided by Net-tools. Prevent its installation by applying a patch:</para>
<screen><userinput>make</userinput></screen>
<para>The <command>su</command> program from Coreutils wasn't installed in
Chapter 5 because it needed <emphasis>root</emphasis> privilege to do so. We're
going to need it in a few moments for the test suite. Therefore we work around
the problem by installing it now:</para>
<xref linkend="chapter-temporary-tools"/> because it needed
<emphasis>root</emphasis> privilege to do so. We're going to need it in a few
moments for the test suite. Therefore we install it now:</para>
<screen><userinput>make install-root</userinput></screen>
<para>This package has a test suite available which can perform a number of
checks to ensure it built correctly. However, this particular test suite
<para>The test suite of this package
makes some assumptions with regards to the presence of non-root users and
groups that don't apply this early into the LFS build. We therefore create
a dummy system user and two dummy groups to allow the tests to run

7
chapter06/e2fsprogs.xml
View File

@ -49,11 +49,8 @@ of.</para></listitem>
<screen><userinput>make</userinput></screen>
<para>This package has a test suite available which can perform a number of
checks to ensure it built correctly. Should you choose to run it, the
following command will do so:</para>
<screen><userinput>make check</userinput></screen>
<para>To have the results tested, issue:
<userinput>make check</userinput>.</para>
<para>Install most of the package:</para>

7
chapter06/ed.xml
View File

@ -48,11 +48,8 @@ the programs available there is useful in the event of the
<screen><userinput>make</userinput></screen>
<para>This package has a test suite available which can perform a number of
checks to ensure it built correctly. Should you choose to run it, the
following command will do so:</para>
<screen><userinput>make check</userinput></screen>
<para>To have the results tested, issue:
<userinput>make check</userinput>.</para>
<para>Install the package:</para>

7
chapter06/findutils.xml
View File

@ -30,11 +30,8 @@ to the above configure options.</para>
<screen><userinput>make</userinput></screen>
<para>This package has a test suite available which can perform a number of
checks to ensure it built correctly. Should you choose to run it, the
following command will do so:</para>
<screen><userinput>make check</userinput></screen>
<para>To have the results tested, issue:
<userinput>make check</userinput>.</para>
<para>And install the package:</para>

7
chapter06/flex.xml
View File

@ -24,11 +24,8 @@ recognize patterns in text.</para>
<screen><userinput>make</userinput></screen>
<para>This package has a test suite available which can perform a number of
checks to ensure it built correctly. Should you choose to run it, the
following command will do so:</para>
<screen><userinput>make bigcheck</userinput></screen>
<para>To have the results tested, issue:
<userinput>make bigcheck</userinput>.</para>
<para>And install the package:</para>

7
chapter06/gawk.xml
View File

@ -23,11 +23,8 @@
<screen><userinput>make</userinput></screen>
<para>This package has a test suite available which can perform a number of
checks to ensure it built correctly. Should you choose to run it, the
following command will do so:</para>
<screen><userinput>make check</userinput></screen>
<para>To have the results tested, issue:
<userinput>make check</userinput>.</para>
<para>And install the package:</para>

12
chapter06/gettext.xml
View File

@ -25,15 +25,9 @@ localization. These allow programs to be compiled with Native Language Support
<screen><userinput>make</userinput></screen>
<para>This package has a test suite available which performs a number of
checks to ensure it will function correctly. It's worth noting that Gettext
does not play a critical role in the overall operation of an LFS system. In
addition, the Gettext test suite runs for quite a long period of time.
Accordingly, the running of the test suite here is not crucial. Should you
choose to run the Gettext test suite, the following command will do
so:</para>
<screen><userinput>make check</userinput></screen>
<para>To have the results tested, issue:
<userinput>make check</userinput>. This takes a very long time, around
6 SBUs.</para>
<para>And install the package:</para>

7
chapter06/grep.xml
View File

@ -23,11 +23,8 @@
<screen><userinput>make</userinput></screen>
<para>This package has a test suite available which can perform a number of
checks to ensure it built correctly. Should you choose to run it, the
following command will do so:</para>
<screen><userinput>make check</userinput></screen>
<para>To have the results tested, issue:
<userinput>make check</userinput>.</para>
<para>And install the package:</para>

7
chapter06/libtool.xml
View File

@ -25,11 +25,8 @@ interface.</para>
<screen><userinput>make</userinput></screen>
<para>This package has a test suite available which can perform a number of
checks to ensure it built correctly. Should you choose to run it, the
following command will do so:</para>
<screen><userinput>make check</userinput></screen>
<para>To have the results tested, issue:
<userinput>make check</userinput>.</para>
<para>And install the package:</para>

7
chapter06/m4.xml
View File

@ -23,11 +23,8 @@
<screen><userinput>make</userinput></screen>
<para>This package has a test suite available which can perform a number of
checks to ensure it built correctly. Should you choose to run it, the
following command will do so:</para>
<screen><userinput>make check</userinput></screen>
<para>To have the results tested, issue:
<userinput>make check</userinput>.</para>
<para>And install the package:</para>

7
chapter06/make.xml
View File

@ -23,11 +23,8 @@
<screen><userinput>make</userinput></screen>
<para>This package has a test suite available which can perform a number of
checks to ensure it built correctly. Should you choose to run it, the
following command will do so:</para>
<screen><userinput>make check</userinput></screen>
<para>To have the results tested, issue:
<userinput>make check</userinput>.</para>
<para>And install the package:</para>

7
chapter06/perl.xml
View File

@ -36,10 +36,9 @@ program.</para></listitem>
<screen><userinput>make</userinput></screen>
<para>This package has a test suite available which can perform a number of
checks to ensure it built correctly. Should you choose to run it, you first
have to create a basic <filename>/etc/hosts</filename> file, needed by a
couple of tests to resolve the name <emphasis>localhost</emphasis>:</para>
<para>If you wish to run the test suite, you first have to create a basic
<filename>/etc/hosts</filename> file, which is needed by a couple of tests to
resolve the name <emphasis>localhost</emphasis>:</para>
<screen><userinput>echo "127.0.0.1 localhost $(hostname)" &gt; /etc/hosts</userinput></screen>

7
chapter06/sed.xml
View File

@ -23,11 +23,8 @@
<screen><userinput>make</userinput></screen>
<para>This package has a test suite available which can perform a number of
checks to ensure it built correctly. Should you choose to run it, the
following command will do so:</para>
<screen><userinput>make check</userinput></screen>
<para>To have the results tested, issue:
<userinput>make check</userinput>.</para>
<para>And install the package:</para>

7
chapter06/tar.xml
View File

@ -24,11 +24,8 @@
<screen><userinput>make</userinput></screen>
<para>This package has a test suite available which can perform a number of
checks to ensure it built correctly. Should you choose to run it, the
following command will do so:</para>
<screen><userinput>make check</userinput></screen>
<para>To have the results tested, issue:
<userinput>make check</userinput>.</para>
<para>And install the package:</para>

7
chapter06/texinfo.xml
View File

@ -24,11 +24,8 @@ converting Info documents.</para>
<screen><userinput>make</userinput></screen>
<para>This package has a test suite available which can perform a number of
checks to ensure it built correctly. Should you choose to run it, the
following command will do so:</para>
<screen><userinput>make check</userinput></screen>
<para>To have the results tested, issue:
<userinput>make check</userinput>.</para>
<para>Install the package:</para>

13
chapter06/vim.xml
View File

@ -39,14 +39,11 @@ echo '#define SYS_GVIMRC_FILE "/etc/gvimrc"' &gt;&gt; src/feature.h</userinput><
<screen><userinput>make</userinput></screen>
<para>This package has a test suite available which performs a number of
checks to ensure it will function correctly. However, the Vim test suite will
output a whole lot of seemingly garbage characters to screen which can
occasionally wreak havoc with the running terminal. Accordingly, the running of
the test suite here is optional. Should you choose to run the Vim test suite,
the following command will do so:</para>
<screen><userinput>make test</userinput></screen>
<para>To have the results tested, you can issue:
<userinput>make check</userinput>. However, this test suite outputs a lot of
seemingly garbage characters to the screen, and this can wreak havoc with the
settings of the current terminal. Accordingly, the running of the test suite
here is strictly optional.</para>
<para>And install the package:</para>

11
chapter06/zlib.xml
View File

@ -30,10 +30,8 @@ afterwards.</para></note>
<screen><userinput>make</userinput></screen>
<para>This package has a test suite available which can perform a number of
checks to ensure it built correctly. The test suite for Zlib is quick and
painless so we recommend it be run. The following command will test the shared
library:</para>
<para>To have the results tested, issue:
<userinput>make check</userinput>.</para>
<screen><userinput>make check</userinput></screen>
@ -46,9 +44,8 @@ library:</para>
./configure --prefix=/usr
make</userinput></screen>
<para>The following command will test the static library:</para>
<screen><userinput>make check</userinput></screen>
<para>To have the results tested, issue:
<userinput>make check</userinput>.</para>
<para>Install the static library:</para>