[rpms/chromium] epel9-next: - Fix FTBFS on el10.1, error: undefined symbol: __rustc::__rust_alloc_error_handler_should_panic

[rpms/chromium] epel9-next: - Fix FTBFS on el10.1, error: undefined symbol: __rustc::__rust_alloc_error_handler_should_panic

[Than Ngo]

            A new commit has been pushed.

            Repo   : rpms/chromium
            Branch : epel9-next
            Commit : 3f1add43090d3cb2f2074ff436a6e621cfe5e9e4
            Author : Than Ngo <than@redhat.com>
            Date   : 2026-02-16T16:29:06+01:00
            Stats  : +4/-1 in 1 file(s)
            URL    : https://src.fedoraproject.org/rpms/chromium/c/3f1add43090d3cb2f2074ff436a6e621cfe5e9e4?branch=epel9-next

            Log:
            - Fix FTBFS on el10.1, error: undefined symbol: __rustc::__rust_alloc_error_handler_should_panic
- Fix FTBFS on el10.1, error[E0658]: the target feature “avx512f” is currently unstable

---
diff --git a/chromium.spec b/chromium.spec
index cafd840..1a71126 100644
--- a/chromium.spec
+++ b/chromium.spec
@@ -344,7 +344,7 @@ Patch141: chromium-118-dma_buf_export_sync_file-conflict.patch
 #  fix ftbfs caused by old python-3.9 on el8
 Patch142: chromium-143-python-3.9-ftbfs.patch
  
-# fix ftbfs caused by old rustc-1.88 on el9
+# fix ftbfs caused by old rustc-1.88 on el9 and 10.1
 Patch143: chromium-145-rust-1.88-enable-unstable_features.patch
 Patch144: chromium-145-rust-1.88-undefined-symbol.patch
 
@@ -1098,6 +1098,9 @@ Qt6 UI for chromium.
 %if 0%{?rhel} == 8 || 0%{?rhel} == 9
 %patch -P141 -p1 -b .dma_buf_export_sync_file-conflict
 %patch -P142 -p1 -b .python-3.9-ftbfs
+%endif
+
+%if (0%{?rhel} && 0%{?rhel} < 10) || (0%{?rhel} == 10 && 0%{?rhel_minor_version} < 2)
 %patch -P143 -p1 -b .rust-1.88-enable-unstable_features
 %patch -P144 -p1 -b .rustc-1.88-undefined-symbol
 %endif