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: Disable PA_MUSTTAIL to fix build faiure on ppc64le
Date: Fri, 07 Aug 2026 16:07:08 GMT [thread overview]
Message-ID: <178611882846.1.16600513460686679662.rpms-chromium-523675271403@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/chromium
Branch : epel9-next
Commit : 52367527140335f52a69be77de09b544c2740aab
Author : Than Ngo <than@redhat.com>
Date : 2024-11-20T19:53:07+01:00
Stats : +16/-1 in 2 file(s)
URL : https://src.fedoraproject.org/rpms/chromium/c/52367527140335f52a69be77de09b544c2740aab?branch=epel9-next
Log:
Disable PA_MUSTTAIL to fix build faiure on ppc64le
---
diff --git a/HACK-debian-clang-disable-base-musttail.patch b/HACK-debian-clang-disable-base-musttail.patch
index 0ccc45b..fbc9116 100644
--- a/HACK-debian-clang-disable-base-musttail.patch
+++ b/HACK-debian-clang-disable-base-musttail.patch
@@ -6,7 +6,19 @@ diff -up chromium-131.0.6778.69/base/compiler_specific.h.me chromium-131.0.6778.
// }
// ```
-#if __has_cpp_attribute(clang::musttail)
-+#if defined(__clang__) && __has_cpp_attribute(clang::musttail) && !defined(__powerpc64__)
++#if __has_cpp_attribute(clang::musttail) && !defined(__powerpc64__)
#define MUSTTAIL [[clang::musttail]]
#else
#define MUSTTAIL
+diff -up chromium-131.0.6778.85/base/allocator/partition_allocator/src/partition_alloc/partition_alloc_base/compiler_specific.h.me chromium-131.0.6778.85/base/allocator/partition_allocator/src/partition_alloc/partition_alloc_base/compiler_specific.h
+--- chromium-131.0.6778.85/base/allocator/partition_allocator/src/partition_alloc/partition_alloc_base/compiler_specific.h.me 2024-11-20 18:50:28.690761262 +0100
++++ chromium-131.0.6778.85/base/allocator/partition_allocator/src/partition_alloc/partition_alloc_base/compiler_specific.h 2024-11-20 18:54:49.374711202 +0100
+@@ -138,7 +138,7 @@
+ // PA_MUSTTAIL return Func1(d + 1); // `Func1()` will be tail-called.
+ // }
+ // ```
+-#if PA_HAS_CPP_ATTRIBUTE(clang::musttail)
++#if PA_HAS_CPP_ATTRIBUTE(clang::musttail) && !defined(__powerpc64__)
+ #define PA_MUSTTAIL [[clang::musttail]]
+ #else
+ #define PA_MUSTTAIL
diff --git a/chromium.spec b/chromium.spec
index 14a769b..4d54d17 100644
--- a/chromium.spec
+++ b/chromium.spec
@@ -146,6 +146,9 @@
# enable|disable use_custom_libcxx
%global use_custom_libcxx 0
+%if 0%{?rhel} || 0%{?fedora} == 39
+%global use_custom_libcxx 1
+%endif
# enable|disable control flow integrity support
%global cfi 0
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=178611882846.1.16600513460686679662.rpms-chromium-523675271403@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