mirror of
https://git.linuxfromscratch.org/lfs.git
synced 2025-06-18 19:29:21 +01:00
Merge branch 'trunk' of git.linuxfromscratch.org:lfs into trunk
This commit is contained in:
commit
491de3316a
@ -78,11 +78,21 @@
|
||||
|
||||
<screen><userinput remap="make">make</userinput></screen>
|
||||
|
||||
<para>Running the tests at this point is not recommended. The
|
||||
tests are known to hang indefinitely in the partial LFS environment.
|
||||
If desired, the tests can be rerun at the end of this chapter, or
|
||||
when Python 3 is reinstalled in BLFS. To run the tests anyway,
|
||||
issue <command>make test</command>.</para>
|
||||
<para>Some tests are known to occasionally hang indefinitely. So to test the
|
||||
results, run the test suite but set a 2-minute time limit for each
|
||||
test case:</para>
|
||||
|
||||
<screen><userinput remap="test">make test TESTOPTS="--timeout 120"</userinput></screen>
|
||||
|
||||
<para>For a relatively slow system you may need to increase the time
|
||||
limit and 1 SBU (measured when building Binutils pass 1 with one CPU
|
||||
core) should be enough. Some tests are flaky, so the test suite will
|
||||
automatically re-run failed tests. If a test failed but then passed
|
||||
when re-run, it should be considered as passed.</para>
|
||||
|
||||
<para>Two tests named <filename>test_xml_etree</filename> and
|
||||
<filename>test_xml_etree_c</filename> are known to fail with expat-2.6.0
|
||||
or newer.</para>
|
||||
|
||||
<para>Install the package:</para>
|
||||
|
||||
|
@ -93,7 +93,14 @@
|
||||
|
||||
<screen><userinput remap="make">make</userinput></screen>
|
||||
|
||||
<para>If desired, run the test suite as a non-&root; user:</para>
|
||||
<!-- To editors:
|
||||
Two tests need a /etc/fstab file. They are skipped if the host
|
||||
distro isn't using systemd as the init system, so don't remove
|
||||
the creation of /etc/fstab unless you've tested it with such a
|
||||
host distro (for example LFS systemd or Debian). -->
|
||||
<para>If desired, create a dummy <filename>/etc/fstab</filename> file
|
||||
to satisfy two tests and run the test suite as a non-&root;
|
||||
user:</para>
|
||||
|
||||
<warning><para>Running the test suite as the
|
||||
<systemitem class="username">root</systemitem> user can be harmful to
|
||||
@ -106,7 +113,8 @@
|
||||
<screen role="nodump"><userinput>bash tests/run.sh --srcdir=$PWD --builddir=$PWD</userinput></screen>
|
||||
</warning>
|
||||
|
||||
<screen><userinput remap="test">chown -R tester .
|
||||
<screen><userinput remap="test">touch /etc/fstab
|
||||
chown -R tester .
|
||||
su tester -c "make -k check"</userinput></screen>
|
||||
|
||||
<para>
|
||||
|
@ -1 +1 @@
|
||||
6.7.4
|
||||
6.8.2
|
||||
|
@ -144,7 +144,7 @@
|
||||
<!ENTITY e2fsprogs-size "9,412 KB">
|
||||
<!ENTITY e2fsprogs-url "https://downloads.sourceforge.net/project/e2fsprogs/e2fsprogs/v&e2fsprogs-version;/e2fsprogs-&e2fsprogs-version;.tar.gz">
|
||||
<!ENTITY e2fsprogs-md5 "6b4f18a33873623041857b4963641ee9">
|
||||
<!ENTITY e2fsprogs-home "http://e2fsprogs.sourceforge.net/">
|
||||
<!ENTITY e2fsprogs-home "https://e2fsprogs.sourceforge.net/">
|
||||
<!ENTITY e2fsprogs-fin-du "95 MB">
|
||||
<!ENTITY e2fsprogs-fin-sbu "2.4 SBU on a spinning disk, 0.4 SBU on an SSD">
|
||||
|
||||
@ -703,7 +703,7 @@
|
||||
<!ENTITY tcl-size "11,355 KB">
|
||||
<!ENTITY tcl-url "https://downloads.sourceforge.net/tcl/tcl&tcl-version;-src.tar.gz">
|
||||
<!ENTITY tcl-md5 "c30b57c6051be28fa928d09aca82841e">
|
||||
<!ENTITY tcl-home "http://tcl.sourceforge.net/">
|
||||
<!ENTITY tcl-home "https://tcl.sourceforge.net/">
|
||||
<!ENTITY tcl-docs-url "https://downloads.sourceforge.net/tcl/tcl&tcl-version;-html.tar.gz">
|
||||
<!ENTITY tcl-docs-md5 "5467198f8d57c54835bf80b98ffb0170">
|
||||
<!ENTITY tcl-docs-size "1,167 KB">
|
||||
|
@ -114,7 +114,7 @@
|
||||
<para>Do not use any method except the <command>tar</command> command
|
||||
to extract the source code. Notably, using the <command>cp -R</command>
|
||||
command to copy the
|
||||
source code tree somewhere else can destroy links and
|
||||
source code tree somewhere else can destroy
|
||||
timestamps in the source tree, and cause the build to fail.</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
|
Loading…
Reference in New Issue
Block a user