This affects multiple rust crates, and multiple packages that consume those crates, and most upstreams have separate discussions on this. This is a catch-all bug to block all relevant keywording/stabilizations on ppc that are stuck because they need this bug addressed. Sample of what this looks like: error[E0432]: unresolved import `std::sync::atomic::AtomicI64` --> /var/tmp/portage/dev-python/watchfiles-0.21.0-r1/work/cargo_home/gentoo/pyo3-0.20.0/src/impl_/pymodule.rs:6:25 | 6 | use std::sync::atomic::{AtomicI64, Ordering}; | ^^^^^^^^^ | | | no `AtomicI64` in `sync::atomic` | help: a similar name exists in the module: `AtomicI32` For more information about this error, try `rustc --explain E0432`. error: could not compile `pyo3` (lib) due to previous error More links will be added as this is catalogued. Reproducible: Always
This affects 32-bit mips as well, apparently.
pyo3-0.20.0 For the record this particular crate had this issue introduced in 0.20.0 (0.19.x is fine) and was fixed 0.21.0[1] [1] https://github.com/PyO3/pyo3/issues/3614
(In reply to Ionen Wolkens from comment #2) > pyo3-0.20.0 > > For the record this particular crate had this issue introduced in 0.20.0 > (0.19.x is fine) and was fixed 0.21.0[1] My bad, I thought it was in 0.21.0 -- looks like it's not released yet.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d213d850caf1be8141103f0c053581e0fd587da5 commit d213d850caf1be8141103f0c053581e0fd587da5 Author: Mike Gilbert <floppym@gentoo.org> AuthorDate: 2024-11-17 16:21:29 +0000 Commit: Mike Gilbert <floppym@gentoo.org> CommitDate: 2024-11-17 16:21:29 +0000 profiles/arch/powerpc/ppc32: mask sys-fs/lvm2[thin] Bug: https://bugs.gentoo.org/922236 Bug: https://bugs.gentoo.org/930724 Signed-off-by: Mike Gilbert <floppym@gentoo.org> profiles/arch/powerpc/ppc32/package.use.mask | 4 ++++ 1 file changed, 4 insertions(+)
