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

error[E0463]: can't find crate for panic_abort" on ESP32-C3 #87

Open
JuliDi opened this issue Feb 1, 2023 · 1 comment
Open

error[E0463]: can't find crate for panic_abort" on ESP32-C3 #87

JuliDi opened this issue Feb 1, 2023 · 1 comment
Labels
upstream an issue in some upstream dependency

Comments

@JuliDi
Copy link

JuliDi commented Feb 1, 2023

Hi,

When trying to run call stack for my ESP32-C3 I get the error "error[E0463]: can't find crate for panic_abort"

The command I run is cargo +nightly call-stack --bin my_bin --target riscv32imc-esp-espidf > cg.dot

In my cargo config I already have the corresponding options for build-std set:

[unstable]
build-std = ["panic_abort", "std"]
build-std-features = ["panic_immediate_abort"]

An also tried the -Z build-std=panic_abort,std parameters suggested in other issues.
I see that panic_abort is built:
Compiling panic_abort v0.0.0 (/Users/user/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/src/rust/library/panic_abort)
but when it is almost done compiling, it will throw the above error.

Is there any fix for this?

@japaric
Copy link
Owner

japaric commented Feb 27, 2023

cargo b -Z build-std --target x86_64-unknown-linux-gnu works on a fresh cargo new --bin hello project whereas cargo b -Z build-std --target riscv32imc-esp-espidf does not, so I consider this a upstream bug in the standard library and/or Cargo's build-std feature

@japaric japaric added the upstream an issue in some upstream dependency label Feb 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
upstream an issue in some upstream dependency
Projects
None yet
Development

No branches or pull requests

2 participants