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 condition for clang++-unsupported-argument
Date: Fri, 07 Aug 2026 16:07:49 GMT	[thread overview]
Message-ID: <178611886959.1.9446180931026686383.rpms-chromium-b1015a3ed4b7@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/chromium
            Branch : epel9-next
            Commit : b1015a3ed4b7b3ba2bb949fecbc08578d5c50f73
            Author : Than Ngo <than@redhat.com>
            Date   : 2025-05-28T16:43:00+02:00
            Stats  : +1/-33 in 2 file(s)
            URL    : https://src.fedoraproject.org/rpms/chromium/c/b1015a3ed4b7b3ba2bb949fecbc08578d5c50f73?branch=epel9-next

            Log:
            - Fix condition for clang++-unsupported-argument
- Remove useless chromium-133-rust-crc32fast.patch

---
diff --git a/chromium-133-rust-crc32fast.patch b/chromium-133-rust-crc32fast.patch
deleted file mode 100644
index 838a53b..0000000
--- a/chromium-133-rust-crc32fast.patch
+++ /dev/null
@@ -1,11 +0,0 @@
-diff -up chromium-133.0.6943.53/third_party/rust/crc32fast/v1/BUILD.gn.me chromium-133.0.6943.53/third_party/rust/crc32fast/v1/BUILD.gn
---- chromium-133.0.6943.53/third_party/rust/crc32fast/v1/BUILD.gn.me	2025-02-11 00:13:06.132152874 +0100
-+++ chromium-133.0.6943.53/third_party/rust/crc32fast/v1/BUILD.gn	2025-02-11 00:28:22.785233997 +0100
-@@ -41,7 +41,6 @@ cargo_crate("lib") {
-   proc_macro_configs += [ "//build/config/compiler:no_chromium_code" ]
-   deps = [ "//third_party/rust/cfg_if/v1:lib" ]
-   features = [
--    "nightly",
-     "std",
-   ]
-   rustflags = [

diff --git a/chromium.spec b/chromium.spec
index c1b0827..c00ba2c 100644
--- a/chromium.spec
+++ b/chromium.spec
@@ -4,20 +4,8 @@
 # enable|disable system build flags
 %global system_build_flags 0
 
-# set default numjobs for the koji build
-%ifarch aarch64
-%global numjobs 8
-%else
 %global numjobs %{_smp_build_ncpus}
-%endif
-
-# enable|disable all cpus for the build.
-%global use_all_cpus 1
 
-%if %{use_all_cpus}
-%global numjobs %{_smp_build_ncpus}
-%endif
- 
 # official builds have less debugging and go faster... but we have to shut some things off.
 %global official_build 1
 
@@ -333,9 +321,6 @@ Patch309: chromium-132-el8-unsupport-rustc-flags.patch
 # enable fstack-protector-strong
 Patch312: chromium-123-fstack-protector-strong.patch
 
-# build error stdarch_arm_crc32
-Patch313: chromium-133-rust-crc32fast.patch
-
 # old rust version causes build error on el8:
 # error[E0599]: no method named `is_none_or` found for enum `Option` in the current scope
 Patch314: chromium-136-rust-skrifa-build-error.patch
@@ -1051,18 +1036,12 @@ Qt6 UI for chromium.
 
 %patch -P312 -p1 -b .fstack-protector-strong
 
-%ifarch aarch64
-%if 0%{?rhel} == 8 || 0%{?rhel} == 9
-%patch -P313 -p1 -b .rust-crc32fast
-%endif
-%endif
-
 %if 0%{?rhel}
 %patch -P315 -p1 -b .rust-libadler2
 %endif
 %patch -P316 -p1 -b .clang-build-flags
 
-%if 0%{?fedora} > 41 || 0%{?rhel} > 9
+%if 0%{?fedora} < 42 || 0%{?rhel} < 10
 %patch -P317 -p1 -b .clang++-unsupported-argument
 %endif
 

                 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=178611886959.1.9446180931026686383.rpms-chromium-b1015a3ed4b7@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