[lfs] 01/05: Merge remote-tracking branch 'origin/trunk' into xry111/arm64

"Git Owner" ([email protected] via lfs-book Mailing List) <[email protected]>
Newsgroups gmane.linux.lfs.book
Message-ID <[email protected]>
This is an automated email from the git hooks/post-receive script.

git pushed a commit to branch xry111/arm64
in repository lfs.

commit 2818ed851a4dcf6b9acd50e63c37ef599140def3
Merge: 4e577da23 45a285db9
Author: Xi Ruoyao <[email protected]>
AuthorDate: Tue Feb 10 09:32:20 2026 +0800

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

 appendices/dependencies.xml     |  15 +--
 chapter01/changelog.xml         | 265 ++++++++++++++++++++++++++++++++++++++++
 chapter01/whatsnew.xml          |  78 ++++++------
 chapter03/introduction.xml      |  23 ++--
 chapter03/patches.xml           |   2 +
 chapter05/glibc.xml             |   2 +-
 chapter06/coreutils.xml         |   5 +
 chapter06/m4.xml                |  10 +-
 chapter07/cleanup.xml           |   6 +-
 chapter07/createfiles.xml       |  13 +-
 chapter07/gettext.xml           |   5 +
 chapter08/binutils.xml          |   4 +
 chapter08/bzip2.xml             |  21 ++++
 chapter08/coreutils.xml         |  14 +++
 chapter08/gcc.xml               |  11 ++
 chapter08/gettext.xml           |  13 +-
 chapter08/glibc.xml             |  10 +-
 chapter08/grub.xml              |  14 +--
 chapter08/iana-etc.xml          |   2 +-
 chapter08/kbd.xml               |   9 +-
 chapter08/libcap.xml            |   9 ++
 chapter08/libelf.xml            |  14 ++-
 chapter08/libxcrypt.xml         |   4 +
 chapter08/m4.xml                |  10 +-
 chapter08/python.xml            |  12 +-
 chapter08/readline.xml          |  10 ++
 chapter08/shadow.xml            |  47 +++++--
 chapter08/sqlite.xml            |   2 +-
 chapter08/systemd.xml           |  13 +-
 chapter08/tcl.xml               |   2 +-
 chapter08/udev.xml              |   2 +-
 chapter10/kernel.xml            |   7 ++
 chapter10/kernel/highmem.toml   |   1 +
 chapter10/kernel/highmem.xml    |   7 ++
 chapter10/kernel/kernel.version |   2 +-
 chapter10/kernel/systemd.xml    |   3 +-
 general.ent                     |   5 +-
 lfs-latest-git.php              |   6 +-
 packages.ent                    | 222 ++++++++++++++++-----------------
 patches.ent                     |  12 +-
 40 files changed, 667 insertions(+), 245 deletions(-)

diff --cc chapter08/gcc.xml
index 8285744bd,9f3ba6c70..acd65a2da
--- a/chapter08/gcc.xml
+++ b/chapter08/gcc.xml
@@@ -41,11 -41,19 +41,15 @@@
    <sect2 role="installation">
      <title>Installation of GCC</title>
  
+     <para>First, make a fix required by glibc-2.43 and later:</para>
+ 
+     <screen><userinput remap="pre">sed -i 's/char [*]q/const &amp;/' libgomp/affinity-fmt.c</userinput></screen>
+ 
 -    <para>If building on x86_64, change the default directory name for 64-bit
 -    libraries to <quote>lib</quote>:</para>
 +    <para>On ARM64 hosts, set the default directory name for
 +    64-bit libraries to <quote>lib</quote>:</para>
  
 -<screen><userinput remap="pre">case $(uname -m) in
 -  x86_64)
 -    sed -e '/m64=/s/lib64/lib/' \
 -        -i.orig gcc/config/i386/t-linux64
 -  ;;
 -esac</userinput></screen>
 +<screen><userinput remap="pre">sed -e '/lp64=/s/lib64/lib/' \
 +    -i.orig gcc/config/aarch64/t-aarch64-linux</userinput></screen>
  
      <para>The GCC documentation recommends building GCC in a dedicated build directory:</para>
  
@@@ -192,16 -200,13 +196,23 @@@ su tester -c "PATH=$PATH make -k check"
      url="&test-results;"/> and
      <ulink url="https://gcc.gnu.org/ml/gcc-testresults/"/>.</para>
  
 +    <!-- TODO: why?? -->
 +    <para>On ARM64, many tests in
 +    the <filename class='directory'>c-c++-common/hwasan</filename>
 +    directory are known to fail.
 +    The tests named <filename>locally_streaming_1.c</filename>,
 +    <filename>memset-strict-align-1.c</filename>,
 +    <filename>nonlocal_goto_*.c</filename>,
 +    <filename>pr113618.c</filename>, and
 +    <filename>pr114991.c</filename> are also known to fail.</para>
 +
+     <!-- https://gcc.gnu.org/PR118885 -->
+     <para>Four tests related to <filename>pr90579.c</filename> are known
+     to fail.</para>
+ 
+     <para>Five tests related to <filename>analyzer/strchr-1.c</filename> are known
+     to fail.</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.-->
diff --cc chapter10/kernel.xml
index fd0f3ac21,66e58f46b..2b277e086
--- a/chapter10/kernel.xml
+++ b/chapter10/kernel.xml
@@@ -140,7 -140,24 +140,14 @@@
  
        <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
          href="kernel/systemd.xml"/>
 -   
 -      <para>Enable some additional features if you are building a 64-bit
 -      system.  If you are using menuconfig, enable them in the order of
 -      <parameter>CONFIG_PCI_MSI</parameter> first, then
 -      <parameter>CONFIG_IRQ_REMAP</parameter>, at last
 -      <parameter>CONFIG_X86_X2APIC</parameter> because an option only
 -      shows up after its dependencies are selected.</para>
 -
 -      <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
 -        href="kernel/x2apic.xml"/>
  
+       <para>If you are building a 32-bit system,
+       adjust the configuration so the kernel will
+       be able to use up to 4GB physical RAM:</para>
+ 
+       <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
+         href="kernel/highmem.xml"/>
+ 
        <para>If the partition for the LFS system is in a NVME SSD (i. e. the
        device node for the partition is <filename>/dev/nvme*</filename>
        instead of <filename>/dev/sd*</filename>), enable NVME support or

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.

-- 
http://lists.linuxfromscratch.org/sympa/info/lfs-book
Unsubscribe: See the above information page
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.