Changeset 8a5f906
- Timestamp:
- 02/07/2004 10:48:55 AM (20 years ago)
- Branches:
- 10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v5_1, v5_1_1, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- e8692c5e
- Parents:
- c21999c6
- Location:
- chapter06
- Files:
-
- 21 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter06/autoconf.xml
rc21999c6 r8a5f906 24 24 <screen><userinput>make</userinput></screen> 25 25 26 <para>This package has a test suite available which performs a number of 27 checks to ensure it will function correctly. It's worth noting that Autoconf 28 does not play a critical role in the overall operation of an LFS system. In 29 addition, the Autoconf test suite runs for quite a long period of time. 30 Accordingly, the running of the test suite here is not crucial. Should you 31 choose to run the Autoconf test suite, the following command will do 32 so:</para> 33 34 <screen><userinput>make check</userinput></screen> 26 <para>To have the results tested, issue: 27 <userinput>make check</userinput>.This takes a long time, about 2 SBUs, 28 and is strictly optional.</para> 35 29 36 30 <para>And install the package:</para> -
chapter06/automake.xml
rc21999c6 r8a5f906 25 25 <screen><userinput>make</userinput></screen> 26 26 27 <para>This package has a test suite available which performs a number of 28 checks to ensure it will function correctly. It's worth noting that Automake 29 does not play a critical role in the overall operation of an LFS system. In 30 addition, the Automake test suite runs for quite a long period of time. 31 Accordingly, the running of the test suite here is not crucial. Should you 32 choose to run the Automake test suite, the following command will do 33 so:</para> 34 35 <screen><userinput>make check</userinput></screen> 27 <para>To have the results tested, issue: 28 <userinput>make check</userinput>. This takes a long time, about 4 SBUs, 29 and is strictly optional.</para> 36 30 37 31 <para>Install the package:</para> -
chapter06/bash.xml
rc21999c6 r8a5f906 30 30 <screen><userinput>make</userinput></screen> 31 31 32 <para>This package has a test suite available which can perform a number of 33 checks to ensure it built correctly. Should you choose to run it, the 34 following command will do so:</para> 35 36 <screen><userinput>make tests</userinput></screen> 32 <para>To have the results tested, issue: 33 <userinput>make tests</userinput>.</para> 37 34 38 35 <para>Install the package:</para> -
chapter06/bison.xml
rc21999c6 r8a5f906 29 29 <screen><userinput>make</userinput></screen> 30 30 31 <para>This package has a test suite available which can perform a number of 32 checks to ensure it built correctly. Should you choose to run it, the 33 following command will do so (and takes a long time):</para> 34 35 <screen><userinput>make check</userinput></screen> 31 <para>To have the results tested, issue: 32 <userinput>make check</userinput>.</para> 36 33 37 34 <para>And install the package:</para> -
chapter06/coreutils.xml
rc21999c6 r8a5f906 42 42 43 43 <para>The <command>su</command> program from Coreutils wasn't installed in 44 Chapter 5 because it needed <emphasis>root</emphasis> privilege to do so. We're 45 going to need it in a few moments for the test suite. Therefore we work around 46 the problem by installingit now:</para>44 <xref linkend="chapter-temporary-tools"/> because it needed 45 <emphasis>root</emphasis> privilege to do so. We're going to need it in a few 46 moments for the test suite. Therefore we install it now:</para> 47 47 48 48 <screen><userinput>make install-root</userinput></screen> 49 49 50 <para>This package has a test suite available which can perform a number of 51 checks to ensure it built correctly. However, this particular test suite 50 <para>The test suite of this package 52 51 makes some assumptions with regards to the presence of non-root users and 53 52 groups that don't apply this early into the LFS build. We therefore create -
chapter06/e2fsprogs.xml
rc21999c6 r8a5f906 50 50 <screen><userinput>make</userinput></screen> 51 51 52 <para>This package has a test suite available which can perform a number of 53 checks to ensure it built correctly. Should you choose to run it, the 54 following command will do so:</para> 55 56 <screen><userinput>make check</userinput></screen> 52 <para>To have the results tested, issue: 53 <userinput>make check</userinput>.</para> 57 54 58 55 <para>Install most of the package:</para> -
chapter06/ed.xml
rc21999c6 r8a5f906 49 49 <screen><userinput>make</userinput></screen> 50 50 51 <para>This package has a test suite available which can perform a number of 52 checks to ensure it built correctly. Should you choose to run it, the 53 following command will do so:</para> 54 55 <screen><userinput>make check</userinput></screen> 51 <para>To have the results tested, issue: 52 <userinput>make check</userinput>.</para> 56 53 57 54 <para>Install the package:</para> -
chapter06/findutils.xml
rc21999c6 r8a5f906 31 31 <screen><userinput>make</userinput></screen> 32 32 33 <para>This package has a test suite available which can perform a number of 34 checks to ensure it built correctly. Should you choose to run it, the 35 following command will do so:</para> 36 37 <screen><userinput>make check</userinput></screen> 33 <para>To have the results tested, issue: 34 <userinput>make check</userinput>.</para> 38 35 39 36 <para>And install the package:</para> -
chapter06/flex.xml
rc21999c6 r8a5f906 25 25 <screen><userinput>make</userinput></screen> 26 26 27 <para>This package has a test suite available which can perform a number of 28 checks to ensure it built correctly. Should you choose to run it, the 29 following command will do so:</para> 30 31 <screen><userinput>make bigcheck</userinput></screen> 27 <para>To have the results tested, issue: 28 <userinput>make bigcheck</userinput>.</para> 32 29 33 30 <para>And install the package:</para> -
chapter06/gawk.xml
rc21999c6 r8a5f906 24 24 <screen><userinput>make</userinput></screen> 25 25 26 <para>This package has a test suite available which can perform a number of 27 checks to ensure it built correctly. Should you choose to run it, the 28 following command will do so:</para> 29 30 <screen><userinput>make check</userinput></screen> 26 <para>To have the results tested, issue: 27 <userinput>make check</userinput>.</para> 31 28 32 29 <para>And install the package:</para> -
chapter06/gettext.xml
rc21999c6 r8a5f906 26 26 <screen><userinput>make</userinput></screen> 27 27 28 <para>This package has a test suite available which performs a number of 29 checks to ensure it will function correctly. It's worth noting that Gettext 30 does not play a critical role in the overall operation of an LFS system. In 31 addition, the Gettext test suite runs for quite a long period of time. 32 Accordingly, the running of the test suite here is not crucial. Should you 33 choose to run the Gettext test suite, the following command will do 34 so:</para> 35 36 <screen><userinput>make check</userinput></screen> 28 <para>To have the results tested, issue: 29 <userinput>make check</userinput>. This takes a very long time, around 30 6 SBUs.</para> 37 31 38 32 <para>And install the package:</para> -
chapter06/grep.xml
rc21999c6 r8a5f906 24 24 <screen><userinput>make</userinput></screen> 25 25 26 <para>This package has a test suite available which can perform a number of 27 checks to ensure it built correctly. Should you choose to run it, the 28 following command will do so:</para> 29 30 <screen><userinput>make check</userinput></screen> 26 <para>To have the results tested, issue: 27 <userinput>make check</userinput>.</para> 31 28 32 29 <para>And install the package:</para> -
chapter06/libtool.xml
rc21999c6 r8a5f906 26 26 <screen><userinput>make</userinput></screen> 27 27 28 <para>This package has a test suite available which can perform a number of 29 checks to ensure it built correctly. Should you choose to run it, the 30 following command will do so:</para> 31 32 <screen><userinput>make check</userinput></screen> 28 <para>To have the results tested, issue: 29 <userinput>make check</userinput>.</para> 33 30 34 31 <para>And install the package:</para> -
chapter06/m4.xml
rc21999c6 r8a5f906 24 24 <screen><userinput>make</userinput></screen> 25 25 26 <para>This package has a test suite available which can perform a number of 27 checks to ensure it built correctly. Should you choose to run it, the 28 following command will do so:</para> 29 30 <screen><userinput>make check</userinput></screen> 26 <para>To have the results tested, issue: 27 <userinput>make check</userinput>.</para> 31 28 32 29 <para>And install the package:</para> -
chapter06/make.xml
rc21999c6 r8a5f906 24 24 <screen><userinput>make</userinput></screen> 25 25 26 <para>This package has a test suite available which can perform a number of 27 checks to ensure it built correctly. Should you choose to run it, the 28 following command will do so:</para> 29 30 <screen><userinput>make check</userinput></screen> 26 <para>To have the results tested, issue: 27 <userinput>make check</userinput>.</para> 31 28 32 29 <para>And install the package:</para> -
chapter06/perl.xml
rc21999c6 r8a5f906 37 37 <screen><userinput>make</userinput></screen> 38 38 39 <para>This package has a test suite available which can perform a number of 40 checks to ensure it built correctly. Should you choose to run it, you first 41 have to create a basic <filename>/etc/hosts</filename> file, needed by a 42 couple of tests to resolve the name <emphasis>localhost</emphasis>:</para> 39 <para>If you wish to run the test suite, you first have to create a basic 40 <filename>/etc/hosts</filename> file, which is needed by a couple of tests to 41 resolve the name <emphasis>localhost</emphasis>:</para> 43 42 44 43 <screen><userinput>echo "127.0.0.1 localhost $(hostname)" > /etc/hosts</userinput></screen> -
chapter06/sed.xml
rc21999c6 r8a5f906 24 24 <screen><userinput>make</userinput></screen> 25 25 26 <para>This package has a test suite available which can perform a number of 27 checks to ensure it built correctly. Should you choose to run it, the 28 following command will do so:</para> 29 30 <screen><userinput>make check</userinput></screen> 26 <para>To have the results tested, issue: 27 <userinput>make check</userinput>.</para> 31 28 32 29 <para>And install the package:</para> -
chapter06/tar.xml
rc21999c6 r8a5f906 25 25 <screen><userinput>make</userinput></screen> 26 26 27 <para>This package has a test suite available which can perform a number of 28 checks to ensure it built correctly. Should you choose to run it, the 29 following command will do so:</para> 30 31 <screen><userinput>make check</userinput></screen> 27 <para>To have the results tested, issue: 28 <userinput>make check</userinput>.</para> 32 29 33 30 <para>And install the package:</para> -
chapter06/texinfo.xml
rc21999c6 r8a5f906 25 25 <screen><userinput>make</userinput></screen> 26 26 27 <para>This package has a test suite available which can perform a number of 28 checks to ensure it built correctly. Should you choose to run it, the 29 following command will do so:</para> 30 31 <screen><userinput>make check</userinput></screen> 27 <para>To have the results tested, issue: 28 <userinput>make check</userinput>.</para> 32 29 33 30 <para>Install the package:</para> -
chapter06/vim.xml
rc21999c6 r8a5f906 40 40 <screen><userinput>make</userinput></screen> 41 41 42 <para>This package has a test suite available which performs a number of 43 checks to ensure it will function correctly. However, the Vim test suite will 44 output a whole lot of seemingly garbage characters to screen which can 45 occasionally wreak havoc with the running terminal. Accordingly, the running of 46 the test suite here is optional. Should you choose to run the Vim test suite, 47 the following command will do so:</para> 48 49 <screen><userinput>make test</userinput></screen> 42 <para>To have the results tested, you can issue: 43 <userinput>make check</userinput>. However, this test suite outputs a lot of 44 seemingly garbage characters to the screen, and this can wreak havoc with the 45 settings of the current terminal. Accordingly, the running of the test suite 46 here is strictly optional.</para> 50 47 51 48 <para>And install the package:</para> -
chapter06/zlib.xml
rc21999c6 r8a5f906 31 31 <screen><userinput>make</userinput></screen> 32 32 33 <para>This package has a test suite available which can perform a number of 34 checks to ensure it built correctly. The test suite for Zlib is quick and 35 painless so we recommend it be run. The following command will test the shared 36 library:</para> 33 <para>To have the results tested, issue: 34 <userinput>make check</userinput>.</para> 37 35 38 36 <screen><userinput>make check</userinput></screen> … … 47 45 make</userinput></screen> 48 46 49 <para>The following command will test the static library:</para> 50 51 <screen><userinput>make check</userinput></screen> 47 <para>To have the results tested, issue: 48 <userinput>make check</userinput>.</para> 52 49 53 50 <para>Install the static library:</para>
Note:
See TracChangeset
for help on using the changeset viewer.