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: Fix FTBSF with kernel-7.2.0 (fedora 45 and rhel-11)
Date: Wed, 08 Jul 2026 14:31:43 GMT [thread overview]
Message-ID: <178352110348.1.7750919482828807934.rpms-chromium-8a307a78361f@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/chromium
Branch : epel9
Commit : 8a307a78361f5d9d978aeae900f5a3456e27d0e1
Author : Than Ngo <than@redhat.com>
Date : 2026-07-03T22:28:55+02:00
Stats : +24/-1 in 2 file(s)
URL : https://src.fedoraproject.org/rpms/chromium/c/8a307a78361f5d9d978aeae900f5a3456e27d0e1?branch=epel9
Log:
Fix FTBSF with kernel-7.2.0 (fedora 45 and rhel-11)
---
diff --git a/chromium-150-pt_regs-kernel-7.2.0.patch b/chromium-150-pt_regs-kernel-7.2.0.patch
new file mode 100644
index 0000000..6f1ee3b
--- /dev/null
+++ b/chromium-150-pt_regs-kernel-7.2.0.patch
@@ -0,0 +1,17 @@
+
+Fix build error with new kernel-7.2.0 on ppc64le (fedora 45), pt_regs size is changed
+ error: static assertion failed due to requirement 'sizeof(crashpad::ThreadContext::t64_t) == sizeof(pt_regs)': Size mismatch
+
+diff -up chromium-150.0.7871.46/third_party/crashpad/crashpad/util/linux/thread_info.h.me chromium-150.0.7871.46/third_party/crashpad/crashpad/util/linux/thread_info.h
+--- chromium-150.0.7871.46/third_party/crashpad/crashpad/util/linux/thread_info.h.me 2026-07-03 13:42:51.069732930 +0200
++++ chromium-150.0.7871.46/third_party/crashpad/crashpad/util/linux/thread_info.h 2026-07-03 13:44:52.107066309 +0200
+@@ -165,6 +165,9 @@ union ThreadContext {
+ uint64_t dar;
+ uint64_t dsisr;
+ uint64_t result;
++ uint64_t exit_flags;
++ uint64_t __pt_regs_pad[3];
++
+ #else
+ #error Port.
+ #endif // ARCH_CPU_X86_FAMILY
diff --git a/chromium.spec b/chromium.spec
index a4906f2..2e16cf1 100644
--- a/chromium.spec
+++ b/chromium.spec
@@ -498,6 +498,9 @@ Patch418: 0002-regenerate-xnn-buildgn.patch
Patch419: 0009-sandbox-ignore-byte-span-error.patch
Patch420: 0005-blink-add-audio-vector-support.patch
+# Fix FTBSF with kernel-7.2.0 (fedora 45 and rhel-11)
+Patch450: chromium-150-pt_regs-kernel-7.2.0.patch
+
# flatpak sandbox patches from
# https://github.com/flathub/org.chromium.Chromium/tree/master/patches/chromium
Patch500: flatpak-Add-initial-sandbox-support.patch
@@ -1222,6 +1225,9 @@ Qt6 UI for chromium.
%patch -P418 -p1 -b .0002-regenerate-xnn-buildgn
%patch -P419 -p1 -b .0009-sandbox-ignore-byte-span-error
%patch -P420 -p1 -b .0005-blink-add-audio-vector-support
+%if 0%{?fedora} > 44 || 0%{?rhel} > 10
+%patch -P450 -p1 -b .pt_regs-kernel-7.2.0
+%endif
%endif
%if 0%{?flatpak}
@@ -1685,7 +1691,7 @@ pushd %{chromebuilddir}
cp -a icudtl.dat %{buildroot}%{chromium_path}
%endif
cp -a chrom*.pak resources.pak %{buildroot}%{chromium_path}
- cp -a locales/*.pak %{buildroot}%{chromium_path}/locales/
+ cp --remove-destination locales/*.pak %{buildroot}%{chromium_path}/locales/
cp -a MEIPreload/ PrivacySandboxAttestationsPreloaded/ %{buildroot}%{chromium_path}/
%if %{build_chrome_management_service}
cp -a chrome_management_service %{buildroot}%{chromium_path}/chrome-management-service
reply other threads:[~2026-07-08 14:31 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=178352110348.1.7750919482828807934.rpms-chromium-8a307a78361f@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