-
Notifications
You must be signed in to change notification settings - Fork 386
Miri does not support target x86_64-unknown-uefi #2740
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
The source code for this is https://stackoverflow.com/questions/68455964/how-can-i-execute-tests-in-a-crate-that-gets-developed-for-a-non-default-target (with the failing import removed) |
This will need to be extended to include Lines 284 to 287 in 4f051a6
|
Yeah Miri simply does not support this target currently. Is there a way cargo-miri can figure out the binary file name extension for a target, without us having to maintain a list of all of them? |
I am confused why miri needs to know the extension in the first place? Does cargo not pass the output file name to you? |
|
Nope.
Ah, that should work for Miri as well then. |
cargo-miri: use rustc to determine the output filename This should fix rust-lang/miri#2740 and fix rust-lang/miri#1867: we no longer need to hard-code the file name logic in cargo-miri.
I am not quite sure what's going on here, but @oli-obk thinks it's a bug in miri itself, unrelated to cargo or the standard library.
The text was updated successfully, but these errors were encountered: