[lfs] 02/02: loongarch: Revert "loongarch: binutils: Fix linker relaxation symbol size issue"

"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/loongarch
in repository lfs.

commit 604c6d48ec52a6a5472ca9b5693a98ae4830f5f4
Author: Xi Ruoyao <[email protected]>
AuthorDate: Sun Nov 16 02:30:36 2025 +0800

    loongarch: Revert "loongarch: binutils: Fix linker relaxation symbol size issue"
    
    This reverts commit cc25a45581c5b2fea5e8d93b216f525109b57815.
    
    The patch is in binutils-2.45.1.
---
 chapter03/patches.xml        | 4 ++--
 chapter05/binutils-pass1.xml | 4 ----
 chapter06/binutils-pass2.xml | 4 ----
 chapter08/binutils.xml       | 4 ----
 patches.ent                  | 4 ----
 5 files changed, 2 insertions(+), 18 deletions(-)

diff --git a/chapter03/patches.xml b/chapter03/patches.xml
index 864f8dea9..d71b204bb 100644
--- a/chapter03/patches.xml
+++ b/chapter03/patches.xml
@@ -34,7 +34,7 @@
       </listitem>
     </varlistentry>
 -->
-
+<!--
     <varlistentry>
       <term>Binutils LoongArch Fix Patch - <token>&binutils-loongarch-patch-size;</token>:</term>
       <listitem>
@@ -42,7 +42,7 @@
         <para>MD5 sum: <literal>&binutils-loongarch-patch-md5;</literal></para>
       </listitem>
     </varlistentry>
-<!--
+
     <varlistentry>
       <term>Binutils Upstream Fixes Patch - <token>&binutils-upstream-patch-size;</token>:</term>
       <listitem>
diff --git a/chapter05/binutils-pass1.xml b/chapter05/binutils-pass1.xml
index 37f0519a8..fe3a1c4a6 100644
--- a/chapter05/binutils-pass1.xml
+++ b/chapter05/binutils-pass1.xml
@@ -53,10 +53,6 @@
     linker and assembler to determine which of their own features to
     enable.</para>
 
-    <para>Apply a patch to fix an issue identified upstream:</para>
-
-    <screen><userinput remap="pre">patch -Np1 -i ../&binutils-loongarch-patch;</userinput></screen>
-
     <para>The Binutils documentation recommends building Binutils
     in a dedicated build directory:</para>
 
diff --git a/chapter06/binutils-pass2.xml b/chapter06/binutils-pass2.xml
index 4c0c22928..a1892a1aa 100644
--- a/chapter06/binutils-pass2.xml
+++ b/chapter06/binutils-pass2.xml
@@ -57,10 +57,6 @@
 
 <screen><userinput remap="pre">sed '6031s/$add_dir//' -i ltmain.sh</userinput></screen>
 
-    <para>Apply a patch to fix an issue identified upstream:</para>
-
-    <screen><userinput remap="pre">patch -Np1 -i ../&binutils-loongarch-patch;</userinput></screen>
-
     <para>Create a separate build directory again:</para>
 
 <screen><userinput remap="pre">mkdir -v build
diff --git a/chapter08/binutils.xml b/chapter08/binutils.xml
index 0542d2d3e..c05a769f2 100644
--- a/chapter08/binutils.xml
+++ b/chapter08/binutils.xml
@@ -41,10 +41,6 @@
   <sect2 role="installation">
     <title>Installation of Binutils</title>
 
-    <para>Apply a patch to fix an issue identified upstream:</para>
-
-    <screen><userinput remap="pre">patch -Np1 -i ../&binutils-loongarch-patch;</userinput></screen>
-
     <para>The Binutils documentation recommends building Binutils
     in a dedicated build directory:</para>
 
diff --git a/patches.ent b/patches.ent
index 35718eb2a..77ffb04d6 100644
--- a/patches.ent
+++ b/patches.ent
@@ -11,10 +11,6 @@
 <!ENTITY binutils-upstream-patch-size "18 KB">
 -->
 
-<!ENTITY binutils-loongarch-patch "binutils-&binutils-version;-loongarch_fix-1.patch">
-<!ENTITY binutils-loongarch-patch-md5 "bfdcc07c063c20f5f786d80a92efa593">
-<!ENTITY binutils-loongarch-patch-size "7.4 KB">
-
 <!ENTITY bzip2-docs-patch "bzip2-&bzip2-version;-install_docs-1.patch">
 <!ENTITY bzip2-docs-patch-md5 "6a5ac7e89b791aae556de0f745916f7f">
 <!ENTITY bzip2-docs-patch-size "1.6 KB">

-- 
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.