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 error: out-of-line definition of 'ProcessARateVector' does not match any declaration in 'blink::Delay'
Date: Fri, 07 Aug 2026 16:08:51 GMT [thread overview]
Message-ID: <178611893118.1.13251371182641991269.rpms-chromium-2fea17aa2a91@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/chromium
Branch : epel9-next
Commit : 2fea17aa2a91c0699471a0259cca0013af65812e
Author : Than Ngo <than@redhat.com>
Date : 2026-03-24T20:07:25+01:00
Stats : +23/-1 in 2 file(s)
URL : https://src.fedoraproject.org/rpms/chromium/c/2fea17aa2a91c0699471a0259cca0013af65812e?branch=epel9-next
Log:
Fix error: out-of-line definition of 'ProcessARateVector' does not match any declaration in 'blink::Delay'
---
diff --git a/chromium-146-ppc64le-build-error.patch b/chromium-146-ppc64le-build-error.patch
new file mode 100644
index 0000000..9f73d6b
--- /dev/null
+++ b/chromium-146-ppc64le-build-error.patch
@@ -0,0 +1,18 @@
+Fix build error on ppc64le
+
+ error: out-of-line definition of 'ProcessARateVector' does not match any declaration in 'blink::Delay'
+
+diff -up chromium-146.0.7680.164/third_party/blink/renderer/platform/audio/delay.cc.me chromium-146.0.7680.164/third_party/blink/renderer/platform/audio/delay.cc
+--- chromium-146.0.7680.164/third_party/blink/renderer/platform/audio/delay.cc.me 2026-03-24 15:38:50.300720592 +0100
++++ chromium-146.0.7680.164/third_party/blink/renderer/platform/audio/delay.cc 2026-03-24 15:54:07.159563910 +0100
+@@ -102,8 +102,8 @@ double Delay::DelayTime(float sample_rat
+ #if !(defined(ARCH_CPU_X86_FAMILY) || defined(CPU_ARM_NEON))
+ // Default scalar versions if simd/neon are not available.
+ std::tuple<size_t, size_t> Delay::ProcessARateVector(
+- float* destination,
+- uint32_t frames_to_process) const {
++ base::span<float> destination,
++ size_t frames_to_process) const {
+ // We don't have a vectorized version, so just do nothing and return the 0 to
+ // indicate no frames processed and return the current write_index_.
+ return std::make_tuple(0, write_index_);
diff --git a/chromium.spec b/chromium.spec
index b59ab63..4b49274 100644
--- a/chromium.spec
+++ b/chromium.spec
@@ -349,7 +349,7 @@ Patch145: chromium-146-ftbfs-rust-bytemuck.patch
# add correct path for Qt6Gui header and libs
Patch150: chromium-124-qt6.patch
-# fix FTFS caused by missing include file on aarch64/ppc64le
+# fix FTBFS caused by missing include file on aarch64/ppc64le
Patch300: chromium-145-swiftshader-missing-include.patch
# Fix error with llwm < 21 on el9/el10.1/f42: invalid application of 'sizeof' to an incomplete type 'gfx::Transform'
@@ -491,6 +491,9 @@ Patch417: 0001-add-xnn-ppc64el-support.patch
Patch418: 0002-regenerate-xnn-buildgn.patch
Patch419: 0009-sandbox-ignore-byte-span-error.patch
+# Fix FTBFS, error: out-of-line definition of 'ProcessARateVector' does not match any declaration in 'blink::Delay'
+Patch420: chromium-146-ppc64le-build-error.patch
+
# flatpak sandbox patches from
# https://github.com/flathub/org.chromium.Chromium/tree/master/patches/chromium
Patch500: flatpak-Add-initial-sandbox-support.patch
@@ -1198,6 +1201,7 @@ Qt6 UI for chromium.
%patch -P417 -p1 -b .0001-add-xnn-ppc64el-support
%patch -P418 -p1 -b .0002-regenerate-xnn-buildgn
%patch -P419 -p1 -b .0009-sandbox-ignore-byte-span-error
+%patch -P420 -p1 -b .fix-ppc64le-build-error
%endif
%if 0%{?flatpak}
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=178611893118.1.13251371182641991269.rpms-chromium-2fea17aa2a91@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