We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
wasmer create-exe
wasmer -vV; rustc -vV wasmer 5.0.4 (??????? 2025-02-17) binary: wasmer-cli commit-hash: commit-date: 2025-02-17 host: x86_64-unknown-linux-gnu compiler: singlepass,cranelift,llvm c_api backend: rustc 1.86.0-beta.4 (61e1603ac 2025-03-02) binary: rustc commit-hash: 61e1603ac7b9162968f55a4e9f6f136c0e1bf68a commit-date: 2025-03-02 host: x86_64-unknown-linux-gnu release: 1.86.0-beta.4 LLVM version: 19.1.7
fn main() { println!("Hello, world!"); }
rustc test.rs --target wasm32-wasip1
wasmer create-exe -o test test.wasm -v
Compiler: cranelift Target: x86_64-unknown-linux-gnu Using path `/home/magicloud/.wasmer/cache/wasmer-linux-amd64/lib/libwasmer-headless.a` as libwasmer path. ✔ Native executable compiled successfully to `test`.
./test
Failed to create module from atom "test" Error len: `65` incompatible binary: The provided bytes are not wasmer-universal
--llvm
Expected to get an executable output "Hello, world!".
The executable somehow seems broken.
I saw another issue mentioned that cranelift worked for him but not llvm. But for me, neither works. So I start a new issue.
cranelift
llvm
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
Steps to reproduce
rustc test.rs --target wasm32-wasip1
wasmer create-exe -o test test.wasm -v
./test
--llvm
failed the same wayExpected behavior
Expected to get an executable output "Hello, world!".
Actual behavior
The executable somehow seems broken.
Additional context
I saw another issue mentioned that
cranelift
worked for him but notllvm
. But for me, neither works. So I start a new issue.The text was updated successfully, but these errors were encountered: