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: fixed compiler error on el7 - error: defaulting this default constructor would delete it after its first declaration
Date: Fri, 07 Aug 2026 16:05:29 GMT [thread overview]
Message-ID: <178611872968.1.18055240737283170010.rpms-chromium-18a48bd7aa36@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/chromium
Branch : epel9-next
Commit : 18a48bd7aa36b1f368e817a8bd4c35166c162edc
Author : Than Ngo <than@redhat.com>
Date : 2023-09-16T23:05:36+02:00
Stats : +15/-0 in 2 file(s)
URL : https://src.fedoraproject.org/rpms/chromium/c/18a48bd7aa36b1f368e817a8bd4c35166c162edc?branch=epel9-next
Log:
fixed compiler error on el7 - error: defaulting this default constructor would delete it after its first declaration
---
diff --git a/chromium-117-el7-default_constructor.patch b/chromium-117-el7-default_constructor.patch
new file mode 100644
index 0000000..1b386b6
--- /dev/null
+++ b/chromium-117-el7-default_constructor.patch
@@ -0,0 +1,13 @@
+diff -up chromium-117.0.5938.62/content/browser/interest_group/header_direct_from_seller_signals.cc.me chromium-117.0.5938.62/content/browser/interest_group/header_direct_from_seller_signals.cc
+--- chromium-117.0.5938.62/content/browser/interest_group/header_direct_from_seller_signals.cc.me 2023-09-16 09:43:41.717545215 +0200
++++ chromium-117.0.5938.62/content/browser/interest_group/header_direct_from_seller_signals.cc 2023-09-16 09:48:07.319539585 +0200
+@@ -187,7 +187,8 @@ void OnJsonDecoded(std::unique_ptr<const
+
+ } // namespace
+
+-HeaderDirectFromSellerSignals::HeaderDirectFromSellerSignals() = default;
++HeaderDirectFromSellerSignals::HeaderDirectFromSellerSignals() :
++ seller_signals_(absl::nullopt), auction_signals_(absl::nullopt) { }
+
+ HeaderDirectFromSellerSignals::~HeaderDirectFromSellerSignals() = default;
+
diff --git a/chromium.spec b/chromium.spec
index 3197d6c..5e62bbf 100644
--- a/chromium.spec
+++ b/chromium.spec
@@ -325,6 +325,7 @@ Patch107: chromium-99.0.4844.51-el7-extra-operator.patch
Patch109: chromium-114-wireless-el7.patch
Patch110: chromium-115-buildflag-el7.patch
Patch111: chromium-116-constexpr.patch
+Patch112: chromium-117-el7-default_constructor.patch
# system ffmpeg
Patch114: chromium-107-ffmpeg-duration.patch
@@ -941,6 +942,7 @@ udev.
%patch -P109 -p1 -b .wireless
%patch -P110 -p1 -b .buildflag-el7
%patch -P111 -p1 -b .constexpr
+%patch -P112 -p1 -b .default_constructor
%endif
%if 0%{?rhel} == 9
reply other threads:[~2026-08-07 16:05 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=178611872968.1.18055240737283170010.rpms-chromium-18a48bd7aa36@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