-
Notifications
You must be signed in to change notification settings - Fork 33
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
"riscv32imc_zicsr_zifencei-esp-espidf" unknown target #285
Comments
It's not a compiler problem but one of target detection in the |
From memory the behaviour change in cc-rs was introduced in cc-rs v1.1.32. So a older version there should work |
I now tried pinning it to 1.1.20 in my Cargo.toml [build-dependencies]
embuild = "0.32.0"
vergen-gix = { version = "1", features = ["build", "rustc"] }
anyhow = "1"
cc = "1.1.20" But that didn't help. Sorry for being a noob here! |
can you show what actual cc-rs version is in your dependency graph via |
Ah, yes! That did the trick! Thank you! Do I keep this issue open? Or is this not a real issue? IMO it is, as it breaks current setups. |
It is already fixed in what we can do inside esp-idf-sys gith repo and cmake-rs, but as you might notice that was a semver incompatible "breaking" change in cc-rs. There is nothing we can do here besides people themself pinning the cc-rs crate, since its a transitive dependancy. So yeah you can use our git branches without the pinning or using the normal crates release version. |
Ah, okay. Thanks! |
I was trying to compile my project https://github.com/mawoka-myblock/td-free, but it's not possible anymore as the target is supposedly not found. Logs can be found in the GitHub action: https://github.com/mawoka-myblock/td-free/actions/runs/12436048066/job/34723097689#step:12:24200
And I've tried that on two different PCs and on in the cloud on GitHub actions. I pinned the nightly to version to the 01.12.2024 one, as it's supposed to work with that, but it doesn't. Latest nightly version produces the same result.
Compiling with "cargo +esp" doesn't help either. I've also tried the nightly version from November 1st, and same problem.
The text was updated successfully, but these errors were encountered: