Skip to content

Compile hashbrown fails with unresolved import crate::sys_common::backtrace #950

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

Closed
That3Percent opened this issue Sep 13, 2019 · 1 comment

Comments

@That3Percent
Copy link

This is my first time attempting to use miri via cargo miri test on one of my crates, second-stack. So, this may be a configuration issue and not necessarily a regression.

I'm using rust nightly 2019-09-13, compiling a crate with no external dependencies. When miri compiles hashbrown it fails with the following output...

   Compiling hashbrown v0.5.0
error[E0432]: unresolved import `crate::sys_common::backtrace`
  --> C:\Users\Zac\.rustup\toolchains\nightly-2019-09-13-x86_64-pc-windows-msvc\lib\rustlib\src\rust\src\libstd\backtrace.rs:98:24
   |
98 | use crate::sys_common::backtrace::{output_filename, lock};
   |                        ^^^^^^^^^ could not find `backtrace` in `sys_common`

@RalfJung
Copy link
Member

Thanks for the report!

This is a duplicate of rust-lang/rust#64410: a recent libstd change broke building libstd with xargo.

Until that is resolved, I recommend using nightly-2019-09-11 as your toolchain. That should work fine.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants