Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deku doesn't compile on ESP32 no-std #375

Open
yanshay opened this issue Nov 11, 2023 · 4 comments
Open

Deku doesn't compile on ESP32 no-std #375

yanshay opened this issue Nov 11, 2023 · 4 comments
Labels
bug Something isn't working upstream

Comments

@yanshay
Copy link

yanshay commented Nov 11, 2023

I'm trying to use Deku on ESP32 no-std, and it doesn't compile. (on std it does work fine)

I added it as instructed to Cargo.toml as
deku = { version = "0.16", default-features = false, features = ["alloc"] }

And I get the error below.

I searched for resolution and I found it is not uncommon with certain targets due to versioning of rust/radium, I've seen all kinds of related bugs elsewhere being closed long time ago, tried using all kinds of features on radium/bitvec but couldn't get this solved.
I think it has to do with bitvec still using an old version of radium that decides on which Atomics are available based on all kinds of heuristics and it doesn't recognize them all, but couldn't find any way to force it in in any way to understand Atomic64 is not available for my target.

Any ideas how to resolve this? I don't mind any hacky solution since it practically means all the work I've done can't be used on the target I planned on using.

   Compiling radium v0.7.0
error[E0432]: unresolved imports `core::sync::atomic::AtomicI64`, `core::sync::atomic::AtomicU64`
  --> /Users/yanivshaya/.cargo/registry/src/index.crates.io-6f17d22bba15001f/radium-0.7.0/src/lib.rs:53:34
   |
53 |         use core::sync::atomic::{AtomicI64, AtomicU64};
   |                                  ^^^^^^^^^  ^^^^^^^^^ no `AtomicU64` in `sync::atomic`
   |                                  |
   |                                  no `AtomicI64` in `sync::atomic`
   |
help: a similar name exists in the module
   |
53 |         use core::sync::atomic::{AtomicI32, AtomicU64};
   |                                  ~~~~~~~~~
help: a similar name exists in the module
   |
53 |         use core::sync::atomic::{AtomicI64, AtomicU32};
   |                                             ~~~~~~~~~
@yanshay
Copy link
Author

yanshay commented Nov 11, 2023

I found a way to get this to compile by adding to Cargo.toml:

[patch.crates-io]
bitvec = {git = "https://github.com/arctic-alpaca/ferrilab"}

This forces project to use a fork of bitvec that has been updated to use a new version of radium.

@wcampbell0x2a
Copy link
Collaborator

Looks like artic-alpaca has already notified the bitvec author ferrilab/bitvec#214.

@ProfFan
Copy link

ProfFan commented Nov 15, 2023

The bitvec library has not been maintained for more than half a year now, the issue was closed and there's no activity since. ferrilab/bitvec#220 seems like a good alternative?

@wcampbell0x2a wcampbell0x2a added the bug Something isn't working label Dec 2, 2023
@ProfFan
Copy link

ProfFan commented Jun 1, 2024

Walking by this issue, seems upstream is still unmaintained :D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working upstream
Projects
None yet
Development

No branches or pull requests

3 participants