diff options
| author | Bruce Dubbs <bdubbs@linuxfromscratch.org> | 2019-02-01 23:36:05 +0000 |
|---|---|---|
| committer | Bruce Dubbs <bdubbs@linuxfromscratch.org> | 2019-02-01 23:36:05 +0000 |
| commit | a2717960c1f27b9946eaf3edd38ba6d0e1bdf1a1 (patch) | |
| tree | 859d2dda70a47253697fb8393eba40796c7e32c1 /chapter06 | |
| parent | 816b85ca12f821f31ffde3351d642aceb123c0dd (diff) | |
Update to bison-3.3.1.
Update to glibc-2.29.
Update to libpipeline-1.5.1.
Update to linux-4.20.6.
Update to meson-0.49.1.
Update to mpfr-4.0.2.
Update to ninja-1.9.0.
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@11506 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Diffstat (limited to 'chapter06')
| -rw-r--r-- | chapter06/glibc.xml | 14 | ||||
| -rw-r--r-- | chapter06/ninja.xml | 8 |
2 files changed, 11 insertions, 11 deletions
diff --git a/chapter06/glibc.xml b/chapter06/glibc.xml index bf5a46d17..40281d957 100644 --- a/chapter06/glibc.xml +++ b/chapter06/glibc.xml @@ -151,7 +151,8 @@ unset GCC_INCDIR</userinput></screen> <para>Generally a few tests do not pass. The test failures listed below are usually safe to ignore.</para> -<screen><userinput remap="test">make check</userinput></screen> +<screen><userinput remap="test">ln -sfnv /tools/lib/ld-linux-x86-64.so.2 /lib/ld-linux-x86-64.so.2 +make check</userinput></screen> <para>You may see some test failures. The Glibc test suite is somewhat dependent on the host system. This is a list of the most common @@ -163,12 +164,12 @@ unset GCC_INCDIR</userinput></screen> <para><emphasis>misc/tst-ttyname</emphasis> is known to fail in the LFS chroot environment.</para> </listitem> - +<!-- <listitem> <para><emphasis>inet/tst-idna_name_classify</emphasis> is known to fail in the LFS chroot environment.</para> </listitem> - +--> <listitem> <para><emphasis>posix/tst-getaddrinfo4</emphasis> and <emphasis>posix/tst-getaddrinfo5</emphasis> @@ -180,14 +181,13 @@ unset GCC_INCDIR</userinput></screen> test may fail for reasons that have not been determined.</para> </listitem> -<!-- <listitem> - <para>The <emphasis>rt/tst-cputimer1</emphasis> and - <emphasis>rt/tst-cpuclock2</emphasis> tests have been known to + <para>The <emphasis>rt/tst-cputimer{1,2,3}</emphasis> + tests have been known to fail. The reason is not completely understood, but indications are that minor timing issues can trigger these failures.</para> </listitem> ---> + <listitem> <para>The math tests sometimes fail when running on systems where the CPU is not a relatively new Intel or diff --git a/chapter06/ninja.xml b/chapter06/ninja.xml index 7b31c3bbb..96533f1fe 100644 --- a/chapter06/ninja.xml +++ b/chapter06/ninja.xml @@ -39,7 +39,7 @@ <sect2 role="installation"> <title>Installation of Ninja</title> - +<!-- <para>When run, ninja normally runs a maximum number of processes in parallel. By default this is the number of cores on the system plus two. In some cases this can overheat a CPU or run a system out @@ -51,9 +51,9 @@ limit the number of parallel processes via an environment variable, NINJAJOBS. <command>For example</command> setting: - <!-- Using <command> here to make the output bold. We really don't want + <!- - Using <command> here to make the output bold. We really don't want users setting this now and experience shows that many users blindly - copy/paste anything in a box. --> + copy/paste anything in a box. - -> <screen>export NINJAJOBS=4</screen> @@ -62,7 +62,7 @@ <para>If desired, install the patch by running:</para> <screen><userinput remap="pre">patch -Np1 -i ../ninja-1.8.2-add_NINJAJOBS_var-1.patch</userinput></screen> - +--> <para>Build Ninja with:</para> <screen><userinput remap="configure">python3 configure.py --bootstrap</userinput></screen> |