-
Notifications
You must be signed in to change notification settings - Fork 54
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 targeting wasm32-unknown-unknown #42
Comments
Dependency on |
@nagisa awesome. Thanks! I’m glad that was easy. |
I would love to see a version of stacker published with this fix. It affects stacker v0.1.10 and unfortunately, a bunch of dependencies that rustfmt-nightly uses took a dependency on that.
Workaround for now is pretty easy though: [patch.crates-io]
stacker = { git = "https://github.com/rust-lang/stacker" } |
Will do within next 15 minutes. |
tmandry
added a commit
to tmandry/rust
that referenced
this issue
Aug 18, 2020
…crum update stacker to 0.1.11 to unbreak build for wasm32-unknown-unknown Like rust-lang#72079, this updates stacker. The related problem is stacker is here rust-lang/stacker#42. It was fixed by switching from `libc::c_void` to `std::ffi::c_void` https://github.com/rust-lang/stacker/pull/43/files.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thanks for adding wasm support as this library was the only one that didn't allow using the Rust compiler in wasm. It seems though that it only works for
wasm32-wasi
and notwasm32-unknown-unknown
. I'm not sure what the fix is.Reproduction steps:
Outputs:
The text was updated successfully, but these errors were encountered: