Automatic merge of trunk into multilib

bootscripts/ChangeLog

@@ -1,3 +1,7 @@
+2024-07-12 Xi Ruoyao <xry111@xry111.site>
+   * In mountvirtfs, recreate /dev/fd correctly if it's already created
+     by the initramfs.
+
 2024-07-06 Bruce Dubbs <bdubbs@linuxfromscratch.org>
    * Add logic to init-functions to only print escape sequences
 	  if stdin and stdout are connected to a terminal.

bootscripts/lfs/init.d/mountvirtfs

@@ -83,7 +83,7 @@ case "${1}" in
       ln -sf /proc/self/fd/2 /dev/stderr || failed=1
 
       log_info_msg2 " ${INFO}/dev/fd"
-      ln -sf /proc/self/fd   /dev/fd     || failed=1
+      ln -sfn /proc/self/fd  /dev/fd     || failed=1
 
       if [ -e /proc/kcore ]; then
          log_info_msg2 " ${INFO}/dev/core"

chapter03/packages.xml

@@ -723,7 +723,7 @@
     </varlistentry>
 
     <varlistentry>
-      <term>Systemd Man Pages(&systemd-version;) - <token>&systemd-man-size;</token>:</term>
+      <term>Systemd Man Pages (&systemd-version;) - <token>&systemd-man-size;</token>:</term>
       <listitem>
         <para>Home page: <ulink url="&systemd-home;"/></para>
         <para>Download: <ulink url="&systemd-man-url;"/></para>

chapter05/binutils-pass1.xml

@@ -76,6 +76,7 @@ cd       build</userinput></screen>
              --disable-nls       \
              --enable-gprofng=no \
              --disable-werror    \
+             --enable-new-dtags  \
              --enable-default-hash-style=gnu</userinput></screen>
 <screen arch="ml_32,ml_x32,ml_all"><userinput remap="configure">../configure --prefix=$LFS/tools       \
              --with-sysroot=$LFS \
@@ -141,6 +142,17 @@ cd       build</userinput></screen>
         </listitem>
       </varlistentry>
 
+      <varlistentry>
+        <term><parameter>--enable-new-dtags</parameter></term>
+        <listitem>
+          <para>This makes the linker use the <quote>runpath</quote> tag for
+          embedding library search paths into executables and shared libraries,
+          instead of the traditional <quote>rpath</quote> tag.  It makes
+          debugging dynamically linked executables easier and works around
+          potential issues in the test suite of some packages.</para>
+        </listitem>
+      </varlistentry>
+
       <varlistentry>
         <term><parameter>--enable-default-hash-style=gnu</parameter></term>
         <listitem>

chapter06/binutils-pass2.xml

@@ -73,6 +73,7 @@ cd       build</userinput></screen>
     --enable-gprofng=no        \
     --disable-werror           \
     --enable-64-bit-bfd        \
+    --enable-new-dtags         \
     --enable-default-hash-style=gnu</userinput></screen>
 <screen arch="ml_32,ml_x32,ml_all"><userinput remap="configure">../configure                   \
     --prefix=/usr              \

chapter08/binutils.xml

@@ -57,6 +57,7 @@ cd       build</userinput></screen>
              --enable-shared     \
              --disable-werror    \
              --enable-64-bit-bfd \
+             --enable-new-dtags  \
              --with-system-zlib  \
              --enable-default-hash-style=gnu</userinput></screen>
 <screen arch="ml_32,ml_x32,ml_all"><userinput remap="configure">../configure --prefix=/usr       \

chapter08/cleanup.xml

@@ -12,7 +12,7 @@
 
   <para>Finally, clean up some extra files left over from running tests:</para>
 
-<screen><userinput>rm -rf /tmp/*</userinput></screen>
+  <screen><userinput>rm -rf /tmp/{*,.*}</userinput></screen>
 
   <para>There are also several files in the /usr/lib and /usr/libexec
   directories with a file name extension of .la. These are "libtool archive"

chapter08/systemd.xml

@@ -225,10 +225,8 @@ ninja test</userinput></screen>
 
     <!-- test-namespace needs /run/systemd/inaccessible/sock, which only exists
          after initializing the system with systemd.  -->
-    <para>Three tests: <literal>systemd:core / test-namespace</literal>,
+    <para>One test named <literal>systemd:core / test-namespace</literal>
-                       <literal>test-loopback</literal>, and 
+    is known to fail in the LFS chroot environment.  Some other tests may
-                       <literal>test-copy</literal>,
-    are known to fail in the LFS chroot environment.  Some other tests may
     fail because they depend on various kernel configuration options.</para>
 
     <para>Install the package:</para>

packages.ent

@@ -391,7 +391,7 @@
 <!ENTITY less-fin-du "12 MB">
 <!ENTITY less-fin-sbu "less than 0.1 SBU">
 
-<!ENTITY lfs-bootscripts-version "20240706">      <!-- Scripts depend on this format -->
+<!ENTITY lfs-bootscripts-version "20240717">      <!-- Scripts depend on this format -->
 <!ENTITY lfs-bootscripts-size "BOOTSCRIPTS-SIZE KB">
 <!ENTITY lfs-bootscripts-url "&downloads-root;lfs-bootscripts-&lfs-bootscripts-version;.tar.xz">
 <!ENTITY lfs-bootscripts-md5 "BOOTSCRIPTS-MD5SUM">