Bug 922236 – multiple rust crates fail to compile on ppc: error[E0432]: unresolved import `std::sync::atomic::AtomicI64`

• Status: CONFIRMED
• Product: Gentoo Linux

[Description matoro 2024-01-16 18:22:23 UTC]

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

[Comment 1 matoro 2024-01-16 18:24:10 UTC]

This affects 32-bit mips as well, apparently.

[Comment 2 Ionen Wolkens 2024-01-16 19:00:10 UTC]

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

[Comment 3 Ionen Wolkens 2024-01-16 19:02:32 UTC]

(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.