public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Leigh Scott <leigh123linux@gmail.com>
To: git-commits@fedoraproject.org
Subject: [rpms/cef] rawhide: Fix build error with rustc 1.95
Date: Thu, 20 Aug 2026 12:21:20 GMT [thread overview]
Message-ID: <178722848066.1.5872026288302440370.rpms-cef-5ceb64d9b1d5@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/cef
Branch : rawhide
Commit : 5ceb64d9b1d52ef3725ce6dea1c0598eb55688f2
Author : Leigh Scott <leigh123linux@gmail.com>
Date : 2026-08-20T13:20:46+01:00
Stats : +65/-0 in 2 file(s)
URL : https://src.fedoraproject.org/rpms/cef/c/5ceb64d9b1d52ef3725ce6dea1c0598eb55688f2?branch=rawhide
Log:
Fix build error with rustc 1.95
---
diff --git a/cef.spec b/cef.spec
index 7554228..df41ecd 100644
--- a/cef.spec
+++ b/cef.spec
@@ -402,6 +402,10 @@ Patch319: chromium-143-swiftshader-llvm-16.0.patch
# Fix clang++: error: unknown argument: '-fsanitize-ignore-for-ubsan-feature=array-bounds'
Patch320: chromium-146-clang-unknown-argument.patch
+# Fix build error with rustc 1.95
+# error[E0425]: cannot find type `LaneCount` in module `core::simd`
+Patch321: chromium-148-rust-1.95-bytemuck-ftbfs.patch
+
# Workaround for https://bugzilla.redhat.com/show_bug.cgi?id=2239523
# https://bugs.chromium.org/p/chromium/issues/detail?id=1145581#c60
# Disable BTI until this is fixed upstream.
@@ -1120,6 +1124,7 @@ mv %{_builddir}/cef-%{cef_commit} ./cef
%patch -P318 -p1 -b .memory-allocator-dcheck-assert-fix
%patch -P319 -p1 -b .swiftshader-llvm-16.0
%patch -P320 -p1 -b .clang-unknown-argument
+%patch -P321 -p1 -b .rust-1.95-bytemuck
%if %{disable_bti}
%patch -P352 -p1 -b .workaround_for_crash_on_BTI_capable_system
diff --git a/chromium-148-rust-1.95-bytemuck-ftbfs.patch b/chromium-148-rust-1.95-bytemuck-ftbfs.patch
new file mode 100644
index 0000000..b911b71
--- /dev/null
+++ b/chromium-148-rust-1.95-bytemuck-ftbfs.patch
@@ -0,0 +1,60 @@
+Fix build error with rustc 1.95
+
+error[E0425]: cannot find type `LaneCount` in module `core::simd`
+ --> ../../third_party/rust/chromium_crates_io/vendor/bytemuck-v1/src/zeroable.rs:234:15
+ |
+234 | core::simd::LaneCount<N>: core::simd::SupportedLaneCount,
+ | ^^^^^^^^^ not found in `core::simd`
+error[E0405]: cannot find trait `SupportedLaneCount` in module `core::simd`
+ --> ../../third_party/rust/chromium_crates_io/vendor/bytemuck-v1/src/zeroable.rs:234:41
+ |
+234 | core::simd::LaneCount<N>: core::simd::SupportedLaneCount,
+ | ^^^^^^^^^^^^^^^^^^ not found in `core::simd`
+error[E0425]: cannot find type `LaneCount` in module `core::simd`
+ --> ../../third_party/rust/chromium_crates_io/vendor/bytemuck-v1/src/pod.rs:155:15
+ |
+155 | core::simd::LaneCount<N>: core::simd::SupportedLaneCount,
+ | ^^^^^^^^^ not found in `core::simd`
+error[E0405]: cannot find trait `SupportedLaneCount` in module `core::simd`
+ --> ../../third_party/rust/chromium_crates_io/vendor/bytemuck-v1/src/pod.rs:155:41
+ |
+155 | core::simd::LaneCount<N>: core::simd::SupportedLaneCount,
+
+diff -up chromium-148.0.7778.96/third_party/rust/chromium_crates_io/vendor/bytemuck-v1/src/pod.rs.me chromium-148.0.7778.96/third_party/rust/chromium_crates_io/vendor/bytemuck-v1/src/pod.rs
+--- chromium-148.0.7778.96/third_party/rust/chromium_crates_io/vendor/bytemuck-v1/src/pod.rs.me 2026-04-28 23:05:57.000000000 +0200
++++ chromium-148.0.7778.96/third_party/rust/chromium_crates_io/vendor/bytemuck-v1/src/pod.rs 2026-05-09 20:39:28.808258788 +0200
+@@ -152,7 +152,6 @@ impl_unsafe_marker_for_simd!(
+ unsafe impl<T, const N: usize> Pod for core::simd::Simd<T, N>
+ where
+ T: core::simd::SimdElement + Pod,
+- core::simd::LaneCount<N>: core::simd::SupportedLaneCount,
+ {
+ }
+
+@@ -165,6 +164,7 @@ where
+ unsafe impl<T, const N: usize> Pod for core::simd::Simd<T, N>
+ where
+ T: core::simd::SimdElement + Pod,
++ core::simd::LaneCount<N>: core::simd::SupportedLaneCount,
+ {
+ }
+
+diff -up chromium-148.0.7778.96/third_party/rust/chromium_crates_io/vendor/bytemuck-v1/src/zeroable.rs.me chromium-148.0.7778.96/third_party/rust/chromium_crates_io/vendor/bytemuck-v1/src/zeroable.rs
+--- chromium-148.0.7778.96/third_party/rust/chromium_crates_io/vendor/bytemuck-v1/src/zeroable.rs.me 2026-04-28 23:05:57.000000000 +0200
++++ chromium-148.0.7778.96/third_party/rust/chromium_crates_io/vendor/bytemuck-v1/src/zeroable.rs 2026-05-09 20:39:28.808258788 +0200
+@@ -231,7 +231,6 @@ impl_unsafe_marker_for_simd!(
+ unsafe impl<T, const N: usize> Zeroable for core::simd::Simd<T, N>
+ where
+ T: core::simd::SimdElement + Zeroable,
+- core::simd::LaneCount<N>: core::simd::SupportedLaneCount,
+ {
+ }
+
+@@ -244,6 +243,7 @@ where
+ unsafe impl<T, const N: usize> Zeroable for core::simd::Simd<T, N>
+ where
+ T: core::simd::SimdElement + Zeroable,
++ core::simd::LaneCount<N>: core::simd::SupportedLaneCount,
+ {
+ }
+
reply other threads:[~2026-08-20 12:21 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=178722848066.1.5872026288302440370.rpms-cef-5ceb64d9b1d5@fedoraproject.org \
--to=leigh123linux@gmail.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