Changeset 161a267 for chapter08

Timestamp:

05/13/2024 04:01:59 PM (4 months ago)

Author:

Xi Ruoyao <xry111@…>

Branches:

xry111/arm64

Children:

c6e4dba

Parents:

f6548ac (diff), 5ff2f2e4 (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the (diff) links above to see all the changes relative to each parent.

Message:

Merge remote-tracking branch 'origin/trunk' into xry111/arm64

Location:

chapter08

Files:

• automake.xml (modified) (1 diff)
• bash.xml (modified) (1 diff)
• coreutils.xml (modified) (1 diff)
• expect.xml (modified) (1 diff)
• gcc.xml (modified) (6 diffs)
• grub.xml (modified) (1 diff)
• inetutils.xml (modified) (1 diff)

chapter08/automake.xml

@@ -63 +63 @@
     logical cores you want to use if you don't want to use all.</para>
 
-    <para>The test t/subobj.sh is known to fail.</para>
+    <para>Out of 2926 tests, 52 are known to fail due to incompatibilities in the 
+    test scripts with gcc-14.1 or later.</para>
 
     <para>Install the package:</para>

chapter08/bash.xml

@@ -50 +50 @@
             --without-bash-malloc     \
             --with-installed-readline \
+            bash_cv_strtold_broken=no \
             --docdir=/usr/share/doc/bash-&bash-version;</userinput></screen>
 

chapter08/coreutils.xml

@@ -128 +128 @@
     environment):</para>
 
-<screen><userinput remap="test">su tester -c "PATH=$PATH make RUN_EXPENSIVE_TESTS=yes check" &lt; /dev/null</userinput></screen>
+<screen><userinput remap="test">su tester -c "PATH=$PATH make -k RUN_EXPENSIVE_TESTS=yes check" \
+   &lt; /dev/null</userinput></screen>
 
     <para>Remove the temporary group:</para>

chapter08/expect.xml

@@ -73 +73 @@
 <screen><userinput remap="pre">tar -C tclconfig -xf ../autoconf-&autoconf-version;.tar.xz --strip-components=2 \
     autoconf-&autoconf-version;/build-aux/config.{guess,sub}</userinput></screen>
+
+    <para>Now, make some changes to allow the package with gcc-14.1 or later:</para>
+
+<screen><userinput remap="pre">patch -Np1 -i ../expect-&expect-version;-gcc14-1.patch</userinput></screen>
 
     <para>Prepare Expect for compilation:</para>

chapter08/gcc.xml

@@ -41 +41 @@
   <sect2 role="installation">
     <title>Installation of GCC</title>
-<!--
-    <para>At first, fix an issue breaking
-    <filename class="libraryfile">libasan.a</filename> building this package
-    with Glibc-2.34 or later:</para>
-
-<screen><userinput remap="pre">sed -e '/static.*SIGSTKSZ/d' \
-    -e 's/return kAltStackSize/return SIGSTKSZ * 4/' \
-    -i libsanitizer/sanitizer_common/sanitizer_posix_libcdep.cpp</userinput></screen>
--->
-<!--
-    <para>First fix a problem with the latest version of glibc:</para>
-
-    <screen><userinput remap="pre">patch -Np1 -i ../&gcc-upstream-fixes-patch;</userinput></screen>
--->
+
     <para>On ARM64 hosts, set the default directory name for
     64-bit libraries to <quote>lib</quote>:</para>
@@ -73 +60 @@
              --enable-default-pie     \
              --enable-default-ssp     \
+             --enable-host-pie        \
              --disable-multilib       \
              --disable-bootstrap      \
@@ -144 +132 @@
       important, but it takes a long time. First-time builders are
       encouraged to run the test suite.  The time to run the tests can be
-      reduced significantly by adding -jx to the <command>make -k check</command> command below,
-      where x is the number of CPU cores on your system.</para>
+      reduced significantly by adding -jx to the <command>make -k check</command> 
+      command below, where x is the number of CPU cores on your system.</para>
     </important>
 
@@ -152 +140 @@
 
 <screen><userinput remap="test">ulimit -s 32768</userinput></screen>
+
+    <para>Now remove/fix several known test failures:</para>
+
+<screen><userinput remap="test">sed -e '/cpython/d'               -i ../gcc/testsuite/gcc.dg/plugin/plugin.exp
+sed -e 's/no-pic /&amp;-no-pie /'     -i ../gcc/testsuite/gcc.target/i386/pr113689-1.c
+sed -e 's/300000/(1|300000)/'     -i ../libgomp/testsuite/libgomp.c-c++-common/pr109062.c
+sed -e 's/{ target nonpic } //' \
+    -e '/GOTPCREL/d'              -i ../gcc/testsuite/gcc.target/i386/fentryname3.c</userinput></screen>
 
     <para>Test the results as a non-privileged user, but do not stop at errors:</para>
@@ -168 +164 @@
     url="&test-results;"/> and
     <ulink url="https://gcc.gnu.org/ml/gcc-testresults/"/>.</para>
-
+<!--
     <para>
-    In gcc tests (out of over 185,000),
-    seven tests in the <filename class='directory'>analyzer</filename>
+    Eight gcc tests (out of over 185,000):
+    <!- - https://gcc.gnu.org/PR106375 - -><filename>pr56837.c</filename>
+    and seven tests in the <filename class='directory'>analyzer</filename>
     directory are known to fail.
 
-    <!-- https://gcc.gnu.org/PR109353 -->
+    <!- - https://gcc.gnu.org/PR109353 - ->
     One libstdc++ test (out of over 15000), <filename>copy.cc</filename>, is
     known to fail.
 
-    For g++, 22 tests (out of approximately 250,000): 14
+    For g++, 21 tests (out of approximately 250,000): 14
     <quote>AddressSanitizer*</quote>
-    tests, 7 <filename>interception-malloc-test-1.C</filename> tests,
-    and one test named <filename>contracts-tmpl-spec2.C</filename> are
+    tests and 7 <filename>interception-malloc-test-1.C</filename> tests, are
     known to fail.
 
-    On ARM64, many tests in the
+    Additionally, several tests in the
+    <filename class='directory'>vect</filename> directory are known to fail
+    if the hardware does not support AVX.</para>
+-->
+
+    <para>On ARM64, many tests in the
     <filename class='directory'>c-c++-common/hwasan</filename>
     directory are known to fail in both gcc and g++ tests<!-- why? -->,
@@ -190 +191 @@
     <!-- https://gcc.gnu.org/PR111124 -->
     <filename class='directory'>g++.dg/modules</filename>
-    directory are known to fail in g++ tests.
-    </para>
-
-    <para>A few unexpected failures cannot always be avoided. The GCC developers
-    are usually aware of these issues, but have not resolved them yet.
+    directory are known to fail in g++ tests.</para>
+
+    <para>A few unexpected failures cannot always be avoided. In some cases
+    test failures depend on the specific hardware of the system.<!--The GCC developers
+    are usually aware of these issues, but have not resolved them yet.-->
     Unless the test results are vastly different from those at the above URL,
     it is safe to continue.</para>

chapter08/grub.xml

@@ -54 +54 @@
       <para>
         If your system has UEFI support and you wish to boot LFS with UEFI,
-        you can skip this package in LFS,
-        and install GRUB with UEFI support (and its dependencies) by following
-        the instructions on
-        <ulink url="&blfs-book;postlfs/grub-efi.html">the BLFS page</ulink>
-        (with <parameter>--target=x86_64</parameter> removed).
+        you need to install GRUB with UEFI support (and its dependencies) by
+        following the instructions on
+        <ulink url="&blfs-book;postlfs/grub-efi.html">the BLFS page</ulink>.
+        You may skip this package, or install this package and the BLFS
+        GRUB for UEFI package without conflict (the BLFS page provides
+        instructions for both cases).
       </para>
     </note>

chapter08/inetutils.xml

@@ -40 +40 @@
   <sect2 role="installation">
     <title>Installation of Inetutils</title>
+
+    <para>First, make the package build with gcc-14.1 or later::</para>
+
+<screen><userinput remap="pre">sed -i 's/def HAVE_TERMCAP_TGETENT/ 1/' telnet/telnet.c</userinput></screen>
 
     <para>Prepare Inetutils for compilation:</para>