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 build error with new pipewire in f43
Date: Fri, 07 Aug 2026 16:07:22 GMT [thread overview]
Message-ID: <178611884228.1.17571409206160523914.rpms-chromium-ed617fb21218@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/chromium
Branch : epel9-next
Commit : ed617fb21218a3fa4be7a5b70f426426edf53912
Author : Than Ngo <than@redhat.com>
Date : 2025-02-12T20:35:07+01:00
Stats : +28/-0 in 2 file(s)
URL : https://src.fedoraproject.org/rpms/chromium/c/ed617fb21218a3fa4be7a5b70f426426edf53912?branch=epel9-next
Log:
Fix build error with new pipewire in f43
---
diff --git a/chromium-133-pipewire-cast.patch b/chromium-133-pipewire-cast.patch
new file mode 100644
index 0000000..670cb70
--- /dev/null
+++ b/chromium-133-pipewire-cast.patch
@@ -0,0 +1,21 @@
+diff -up chromium-133.0.6943.53/third_party/webrtc/modules/video_capture/linux/pipewire_session.cc.me chromium-133.0.6943.53/third_party/webrtc/modules/video_capture/linux/pipewire_session.cc
+--- chromium-133.0.6943.53/third_party/webrtc/modules/video_capture/linux/pipewire_session.cc.me 2025-02-12 19:09:54.742875003 +0100
++++ chromium-133.0.6943.53/third_party/webrtc/modules/video_capture/linux/pipewire_session.cc 2025-02-12 19:12:17.492620559 +0100
+@@ -87,7 +87,7 @@ PipeWireNode::PipeWireNode(PipeWireSessi
+ .param = OnNodeParam,
+ };
+
+- pw_node_add_listener(proxy_, &node_listener_, &node_events, this);
++ pw_node_add_listener((struct pw_node*) proxy_, &node_listener_, &node_events, this);
+ }
+
+ // static
+@@ -119,7 +119,7 @@ void PipeWireNode::OnNodeInfo(void* data
+ uint32_t id = info->params[i].id;
+ if (id == SPA_PARAM_EnumFormat &&
+ info->params[i].flags & SPA_PARAM_INFO_READ) {
+- pw_node_enum_params(that->proxy_, 0, id, 0, UINT32_MAX, nullptr);
++ pw_node_enum_params((struct pw_node*)that->proxy_, 0, id, 0, UINT32_MAX, nullptr);
+ break;
+ }
+ }
diff --git a/chromium.spec b/chromium.spec
index 9bcf736..4058c99 100644
--- a/chromium.spec
+++ b/chromium.spec
@@ -357,6 +357,9 @@ Patch353: chromium-127-aarch64-duplicate-case-value.patch
# remove flag split-threshold-for-reg-with-hint, it's not supported in clang <= 17
Patch354: chromium-126-split-threshold-for-reg-with-hint.patch
+# fix build error with new pipewire in f43
+Patch356: chromium-133-pipewire-cast.patch
+
# fix build error: no member named 'hardware_destructive_interference_size' in namespace 'std'
Patch355: chromium-130-hardware_destructive_interference_size.patch
@@ -1060,6 +1063,10 @@ Qt6 UI for chromium.
%patch -P355 -p1 -b .hardware_destructive_interference_size
+%if 0%{?fedora} > 42
+%patch -P356 -p1 -b .pipewire-cast
+%endif
+
%patch -P358 -p1 -b .rust-clang_lib
%ifarch ppc64le
reply other threads:[~2026-08-07 16:07 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=178611884228.1.17571409206160523914.rpms-chromium-ed617fb21218@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