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: Fix FTBFS: undefined symbol: __rust_no_alloc_shim_is_unstable on epel
Date: Fri, 07 Aug 2026 16:08:08 GMT [thread overview]
Message-ID: <178611888868.1.5073189949436993635.rpms-chromium-751b92fa9611@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/chromium
Branch : epel9-next
Commit : 751b92fa9611a08bb455458c3097afe0f7206637
Author : Than Ngo <than@redhat.com>
Date : 2025-09-04T15:52:56+02:00
Stats : +21/-0 in 2 file(s)
URL : https://src.fedoraproject.org/rpms/chromium/c/751b92fa9611a08bb455458c3097afe0f7206637?branch=epel9-next
Log:
Fix FTBFS: undefined symbol: __rust_no_alloc_shim_is_unstable on epel
---
diff --git a/chromium-rust-no-alloc-shim-is-unstable.patch b/chromium-rust-no-alloc-shim-is-unstable.patch
new file mode 100644
index 0000000..f22d906
--- /dev/null
+++ b/chromium-rust-no-alloc-shim-is-unstable.patch
@@ -0,0 +1,15 @@
+--- 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 @@
+ #[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]
++ #[linkage = "weak"]
++ static __rust_no_alloc_shim_is_unstable: u8 = 0;
++
+ // Mangle the symbol name as rustc expects.
+ #[rustc_std_internal_symbol]
+ #[allow(non_upper_case_globals)]
diff --git a/chromium.spec b/chromium.spec
index 6f293d6..6c9577d 100644
--- a/chromium.spec
+++ b/chromium.spec
@@ -315,6 +315,9 @@ Patch309: chromium-132-el8-unsupport-rustc-flags.patch
# Fix rhbz#2387446, FTBFS with rust-1.89.0
Patch310: chromium-139-rust-FTBFS-suppress-warnings.patch
+# Fix FTBFS: undefined symbol: __rust_no_alloc_shim_is_unstable
+Patch311: chromium-rust-no-alloc-shim-is-unstable.patch
+
# enable fstack-protector-strong
Patch312: chromium-123-fstack-protector-strong.patch
@@ -993,6 +996,9 @@ Qt6 UI for chromium.
%endif
%patch -P310 -p1 -b .rust-FTBFS-suppress-warnings
+%if 0%{?rhel}
+%patch -P311 -p1 -b .rust-no-alloc-shim-is-unstable
+%endif
%patch -P312 -p1 -b .fstack-protector-strong
%if 0%{?rhel} && 0%{?rhel} < 10
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=178611888868.1.5073189949436993635.rpms-chromium-751b92fa9611@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