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: build error: unknown architectural extension on aarch64 (epel and < f39)
Date: Fri, 07 Aug 2026 16:06:16 GMT [thread overview]
Message-ID: <178611877613.1.9451949002574112284.rpms-chromium-b3d20435cbc2@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/chromium
Branch : epel9-next
Commit : b3d20435cbc2739be1c46faaffbb66fa9a572093
Author : Than Ngo <than@redhat.com>
Date : 2024-04-18T14:53:04+02:00
Stats : +57/-0 in 2 file(s)
URL : https://src.fedoraproject.org/rpms/chromium/c/b3d20435cbc2739be1c46faaffbb66fa9a572093?branch=epel9-next
Log:
build error: unknown architectural extension on aarch64 (epel and < f39)
---
diff --git a/chromium-124-libdav1d-aarch64.patch b/chromium-124-libdav1d-aarch64.patch
new file mode 100644
index 0000000..03862e9
--- /dev/null
+++ b/chromium-124-libdav1d-aarch64.patch
@@ -0,0 +1,53 @@
+--- chromium-124.0.6367.60/third_party/dav1d/libdav1d/src/arm/asm.S 2024-04-15 22:34:36.000000000 +0200
++++ chromium-122.0.6261.128/third_party/dav1d/libdav1d/src/arm/asm.S 2024-03-13 00:38:27.000000000 +0100
+@@ -34,50 +34,6 @@
+ #define x18 do_not_use_x18
+ #define w18 do_not_use_w18
+
+-#if HAVE_AS_ARCH_DIRECTIVE
+- .arch AS_ARCH_LEVEL
+-#endif
+-
+-#if HAVE_AS_ARCHEXT_DOTPROD_DIRECTIVE
+-#define ENABLE_DOTPROD .arch_extension dotprod
+-#define DISABLE_DOTPROD .arch_extension nodotprod
+-#else
+-#define ENABLE_DOTPROD
+-#define DISABLE_DOTPROD
+-#endif
+-#if HAVE_AS_ARCHEXT_I8MM_DIRECTIVE
+-#define ENABLE_I8MM .arch_extension i8mm
+-#define DISABLE_I8MM .arch_extension noi8mm
+-#else
+-#define ENABLE_I8MM
+-#define DISABLE_I8MM
+-#endif
+-#if HAVE_AS_ARCHEXT_SVE_DIRECTIVE
+-#define ENABLE_SVE .arch_extension sve
+-#define DISABLE_SVE .arch_extension nosve
+-#else
+-#define ENABLE_SVE
+-#define DISABLE_SVE
+-#endif
+-#if HAVE_AS_ARCHEXT_SVE2_DIRECTIVE
+-#define ENABLE_SVE2 .arch_extension sve2
+-#define DISABLE_SVE2 .arch_extension nosve2
+-#else
+-#define ENABLE_SVE2
+-#define DISABLE_SVE2
+-#endif
+-
+-/* If we do support the .arch_extension directives, disable support for all
+- * the extensions that we may use, in case they were implicitly enabled by
+- * the .arch level. This makes it clear if we try to assemble an instruction
+- * from an unintended extension set; we only allow assmbling such instructions
+- * within regions where we explicitly enable those extensions. */
+-DISABLE_DOTPROD
+-DISABLE_I8MM
+-DISABLE_SVE
+-DISABLE_SVE2
+-
+-
+ /* Support macros for
+ * - Armv8.3-A Pointer Authentication and
+ * - Armv8.5-A Branch Target Identification
diff --git a/chromium.spec b/chromium.spec
index 750851a..c1c1922 100644
--- a/chromium.spec
+++ b/chromium.spec
@@ -460,6 +460,9 @@ Patch315: chromium-124-python3-assignment-expressions.patch
# add -ftrivial-auto-var-init=zero and -fwrapv
Patch316: chromium-122-clang-build-flags.patch
+# build error: unknown architectural extension on aarch64 (epel and < f39)
+Patch317: chromium-124-libdav1d-aarch64.patch
+
# Workaround for https://bugzilla.redhat.com/show_bug.cgi?id=2239523
# https://bugs.chromium.org/p/chromium/issues/detail?id=1145581#c60
# Disable BTI until this is fixed upstream.
@@ -1220,6 +1223,7 @@ udev.
%patch -P307 -p1 -R -b .v8-c++20
%patch -P308 -p1 -R -b .v8-c++20
%patch -P314 -p1 -b .clang16-buildflag
+%patch -P317 -p1 -b .libdav1d-aarch64
%endif
%patch -P310 -p1 -b .missing-header-files
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=178611877613.1.9451949002574112284.rpms-chromium-b3d20435cbc2@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