-
Notifications
You must be signed in to change notification settings - Fork 626
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
wasm32-unknown-emscripten target not working #817
Comments
What is the error message that you're getting? |
Multiple ones, Seems there is some kind of memory access pattern in |
What does |
Can you paste the exact message? We have no idea what produces these messages. |
https://travis-ci.org/stevebob/gfx/jobs/429755777 has a failure message from running
cargo-web is a cargo subcommand that makes it easy to build and run for emscripten. I've run this a few times though, and the tests have always compiled successfully. I tried both asmjs and wasm32. @semtexzv #818 isn't an appropriate fix. Why do you think low level bit manipulation is the problem? Is this a known problem with emscripten? Why would this cause errors in |
Running "cargo test --target=asmjs-unknown-emscripten"
Running this command on #818 correctly builds the crate and generates .js files for tests, even though cargo can't run these on it's own. The result is the same when running "cargo test --target=asmjs-unknown-emscripten" @philipc I know it isn't an appropriate fix, but at least crate is compilling, and we know where the issue is. |
No, we don't know where issue is, because I could run the test successfully. However, updating my rust from 1.28.0 to 1.29.1 caused the problem to start occurring. Can you try rust 1.28? I think this needs to be fixed in rust, not by rewriting Also, this kind of problem has happened before for gfx: rust-lang/rust#47023 |
I can compile it with 1.35 nightly. |
Solved a long time ago, this issue was forgotten. Closing. |
Package can't be compiled for "wasm32-unknown-unknown" target. Even compiling the tests fails with "corrupted double-linked list" error during linking using llc.
Command to reproduce:
cargo web test --target=wasm32-unknown-emscripten
This is probably caused by some low-level bit manipulation code somewhere in the library.
The text was updated successfully, but these errors were encountered: