You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am attempting to use Miri in a bare metal project using my custom target. When I run cargo miri setup --target MY_TARGET, it prepares a sysroot for the target, but fails with:
error[E0464]: multiple candidates for `rmeta` dependency `core` found
--> /home/binds/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/rustc-std-workspace-core/lib.rs:4:9
|
4 | pub use core::*;
| ^^^^
|
= note: candidate #1: /tmp/.tmpSCntaC/target/x86_64-prestige/release/deps/libcore-5484c1dfc1494680.rmeta
= note: candidate #2: /tmp/.tmpSCntaC/target/x86_64-prestige/release/deps/libcore-fe8fccd3bdf8e7b3.rmetaFor more information about this error, try `rustc --explain E0464`.error: could not compile `rustc-std-workspace-core` due to previous error
fatal error: failed to build sysroot: sysroot build failed
I am at a loss for what could be causing this. Even if I cargo clean, the same error occurs. I will put anything I believe relevant to help solve this:
In that case please post over there with your OS details, and the output of cargo miri setup -v. I am at a complete loss about what might be causing this but maybe there's a pattern...
I am attempting to use Miri in a bare metal project using my custom target. When I run
cargo miri setup --target MY_TARGET
, it prepares a sysroot for the target, but fails with:I am at a loss for what could be causing this. Even if I
cargo clean
, the same error occurs. I will put anything I believe relevant to help solve this:rustc -vV
:My custom target:
It seems like JSON targets began to be supported as of #2744, so I don't think its an issue with Miri's support for it.
.cargo/config.toml
:rust-toolchain.toml
:The text was updated successfully, but these errors were encountered: