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] f44: - Fix FTBFS caused by tsc on ppc64le
Date: Tue, 15 Sep 2026 20:48:47 GMT [thread overview]
Message-ID: <178950532771.1.13970605654399529956.rpms-chromium-28137202e8d0@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/chromium
Branch : f44
Commit : 28137202e8d07d3ffa08f1569fdc666a62eeef49
Author : Than Ngo <than@redhat.com>
Date : 2026-09-15T22:44:09+02:00
Stats : +17/-0 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/chromium/c/28137202e8d07d3ffa08f1569fdc666a62eeef49?branch=f44
Log:
- Fix FTBFS caused by tsc on ppc64le
- Replace unbundle python3 with system python3
---
diff --git a/chromium.spec b/chromium.spec
index f835085..6fef9b3 100644
--- a/chromium.spec
+++ b/chromium.spec
@@ -560,6 +560,8 @@ Source13: nodejs-sources.sh
BuildRequires: openssl-devel
%endif
+# TypeScript for ppc64le
+Source14: https://github.com/microsoft/TypeScript/releases/download/v7.0.2/typescript-linux-ppc64.tgz
BuildRequires: golang
BuildRequires: clang
BuildRequires: clang-tools-extra
@@ -1272,6 +1274,21 @@ ln -fs $(which gperf) third_party/gperf/cipd/bin/gperf
mkdir -p third_party/rust-toolchain/bin/
ln -fs $(which rustc) third_party/rust-toolchain/bin/rustc
+# need bundle typescript on ppc64le as workaround for FTBFS
+%ifarch ppc64le
+tar xf %{SOURCE14} -C third_party/typescript/linux-amd64/src/
+pushd third_party/typescript/linux-amd64/src/
+cp package/lib/tsc* lib/
+popd
+%endif
+
+# remove bundle python3 and replace it with system one
+# fix FTBFS on aarch64, ppc64le
+# ERROR at //build/toolchain/concurrent_links.gni:156:19: Script returned non-zero exit code.
+%ifnarch x86_64
+cp $(which python3) third_party/cpython3/host/bin/python3
+%endif
+
%if %{bundlelibusbx}
# no hackity hack hack
%else
reply other threads:[~2026-09-15 20:48 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=178950532771.1.13970605654399529956.rpms-chromium-28137202e8d0@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