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: disable memory tagging for epel7 and epel8 on aarch64 due to old glibc
Date: Fri, 07 Aug 2026 16:06:04 GMT [thread overview]
Message-ID: <178611876413.1.10060033537634276003.rpms-chromium-6a1fa5b914ac@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/chromium
Branch : epel9-next
Commit : 6a1fa5b914ac7dcac2cc9dbdd39e8d23ff5fdeea
Author : Than Ngo <than@redhat.com>
Date : 2024-02-22T20:28:07+01:00
Stats : +23/-0 in 2 file(s)
URL : https://src.fedoraproject.org/rpms/chromium/c/6a1fa5b914ac7dcac2cc9dbdd39e8d23ff5fdeea?branch=epel9-next
Log:
disable memory tagging for epel7 and epel8 on aarch64 due to old glibc
---
diff --git a/chromium-122-arm64-memory_tagging.patch b/chromium-122-arm64-memory_tagging.patch
new file mode 100644
index 0000000..6850e58
--- /dev/null
+++ b/chromium-122-arm64-memory_tagging.patch
@@ -0,0 +1,13 @@
+diff -up chromium-122.0.6261.57/base/allocator/partition_allocator/partition_alloc.gni.me chromium-122.0.6261.57/base/allocator/partition_allocator/partition_alloc.gni
+--- chromium-122.0.6261.57/base/allocator/partition_allocator/partition_alloc.gni.me 2024-02-22 20:22:44.115269845 +0100
++++ chromium-122.0.6261.57/base/allocator/partition_allocator/partition_alloc.gni 2024-02-22 20:23:07.067681890 +0100
+@@ -29,8 +29,7 @@ if (is_nacl) {
+ assert(false, "Unknown CPU: $current_cpu")
+ }
+
+-has_memory_tagging =
+- current_cpu == "arm64" && is_clang && !is_asan && (is_linux || is_android)
++has_memory_tagging = false
+
+ declare_args() {
+ # Causes all the allocations to be routed via allocator_shim.cc. Usually,
diff --git a/chromium.spec b/chromium.spec
index ea5b2ff..5a6db8d 100644
--- a/chromium.spec
+++ b/chromium.spec
@@ -427,6 +427,10 @@ Patch303: chromium-121-typename.patch
# error: invalid operands to binary expression
Patch304: chromium-117-string-convert.patch
+# disable memory tagging in epel7 and epel8 on aarch64 due to new feature IFUNC-Resolver
+# not supported in old glibc < 2.30, error: fatal error: 'sys/ifunc.h' file not found
+Patch305: chromium-122-arm64-memory_tagging.patch
+
Patch306: chromium-119-assert.patch
# compiler errors on epel
@@ -1115,6 +1119,12 @@ udev.
%patch -P130 -p1 -b .revert-av1enc
%endif
+%ifarch aarch64
+%if 0%{?rhel} <= 8
+%patch -P305 -p1 -b .memory_tagging
+%endif
+%endif
+
%if 0%{?rhel} || 0%{?fedora} && 0%{?fedora} < 39
%patch -P307 -p1 -R -b .v8-c++20
%patch -P308 -p1 -R -b .v8-c++20
reply other threads:[~2026-08-07 16:06 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=178611876413.1.10060033537634276003.rpms-chromium-6a1fa5b914ac@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