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: undefined symbol: llvm::MCAsmInfoXCOFF::MCAsmInfoXCOFF()
Date: Fri, 07 Aug 2026 16:06:44 GMT [thread overview]
Message-ID: <178611880407.1.6888600562319184776.rpms-chromium-dd3936a5fb3b@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/chromium
Branch : epel9-next
Commit : dd3936a5fb3b275d13a4a28a6f069b327246205e
Author : Than Ngo <than@redhat.com>
Date : 2024-07-21T11:30:02+02:00
Stats : +6/-2 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/chromium/c/dd3936a5fb3b275d13a4a28a6f069b327246205e?branch=epel9-next
Log:
fix error: undefined symbol: llvm::MCAsmInfoXCOFF::MCAsmInfoXCOFF()
---
diff --git a/chromium.spec b/chromium.spec
index d23c49a..81af9da 100644
--- a/chromium.spec
+++ b/chromium.spec
@@ -465,7 +465,10 @@ Patch410: dawn-fix-typos.patch
Patch411: dawn-fix-ppc64le-detection.patch
# Suppress harmless compiler warning messages that appear on ppc64 due to arch-specific warning flags being passed
-Patch413: fix-unknown-warning-option-messages.diff
+Patch412: fix-unknown-warning-option-messages.diff
+
+# error: undefined symbol: llvm::MCAsmInfoXCOFF::MCAsmInfoXCOFF()
+Patch413: fix-swiftshader-compile.patch
# Use chromium-latest.py to generate clean tarball from released build tarballs, found here:
# http://build.chromium.org/buildbot/official/
@@ -1170,7 +1173,8 @@ Qt6 UI for chromium.
%patch -P410 -p1 -b .dawn-fix-typos
%patch -P411 -p1 -b .dawn-fix-ppc64le-detection
-%patch -P413 -p1 -b .fix-unknown-warning-option-messages
+%patch -P412 -p1 -b .fix-unknown-warning-option-messages
+%patch -P413 -p1 -b .fix-swiftshader-compile
%endif
# Change shebang in all relevant files in this directory and all subdirectories
reply other threads:[~2026-08-07 16:06 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=178611880407.1.6888600562319184776.rpms-chromium-dd3936a5fb3b@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