public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Than Ngo <than@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/chromium] epel9-next: Add __rust_alloc_error_handler_should_panic_v2 to fix the build error:
Date: Fri, 07 Aug 2026 16:08:11 GMT	[thread overview]
Message-ID: <178611889106.1.15940560206143357459.rpms-chromium-44e91a81db04@fedoraproject.org> (raw)

           A new commit has been pushed.

           Repo   : rpms/chromium
           Branch : epel9-next
           Commit : 44e91a81db0454b97bfebb24438419e5cfa485ca
           Author : Than Ngo <than@redhat.com>
           Date   : 2025-09-22T14:44:44+02:00
           Stats  : +11/-10 in 1 file(s)
           URL    : https://src.fedoraproject.org/rpms/chromium/c/44e91a81db0454b97bfebb24438419e5cfa485ca?branch=epel9-next

           Log:
           Add __rust_alloc_error_handler_should_panic_v2 to fix the build error:
undefined symbol: __rust_no_alloc_shim_is_unstab

---
diff --git a/chromium-rust-no-alloc-shim-is-unstable.patch b/chromium-rust-no-alloc-shim-is-unstable.patch
index f22d906..563e0d1 100644
--- a/chromium-rust-no-alloc-shim-is-unstable.patch
+++ b/chromium-rust-no-alloc-shim-is-unstable.patch
@@ -1,15 +1,16 @@
---- chromium-140.0.7339.80/build/rust/allocator/lib.rs	2025-08-29 20:50:09.000000000 +0200
-+++ chromium-139.0.7258.154/build/rust/allocator/lib.rs	2025-08-25 18:10:00.000000000 +0200
-@@ -90,6 +90,12 @@
+diff -up chromium-140.0.7339.185/build/rust/allocator/lib.rs.me chromium-140.0.7339.185/build/rust/allocator/lib.rs
+--- chromium-140.0.7339.185/build/rust/allocator/lib.rs.me	2025-09-22 10:37:11.057152982 +0200
++++ chromium-140.0.7339.185/build/rust/allocator/lib.rs	2025-09-22 14:38:10.367927121 +0200
+@@ -89,6 +89,12 @@ mod both_allocators {
+     #[rustc_std_internal_symbol]
      #[linkage = "weak"]
      fn __rust_no_alloc_shim_is_unstable_v2() {}
- 
-+    // TODO(crbug.com/422538133) Remove after rolling past
-+    // https://github.com/rust-lang/rust/pull/141061
-+    #[no_mangle]
++    
++    #[rustc_std_internal_symbol]
 +    #[linkage = "weak"]
-+    static __rust_no_alloc_shim_is_unstable: u8 = 0;
-+
++    fn __rust_alloc_error_handler_should_panic_v2() -> u8 {
++        0
++    }
+ 
      // Mangle the symbol name as rustc expects.
      #[rustc_std_internal_symbol]
-     #[allow(non_upper_case_globals)]

                 reply	other threads:[~2026-08-07 16:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=178611889106.1.15940560206143357459.rpms-chromium-44e91a81db04@fedoraproject.org \
    --to=than@redhat.com \
    --cc=git-commits@fedoraproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox