stephen (May 02 2025 at 11:04): stephen (May 02 2025 at 11:04):rustup target add wasm32-wasip1 this line from the readme fails for me on mac os 15.4.1
error: toolchain 'stable-aarch64-apple-darwin' does not support target 'wasm32-wasip1'; did you mean 'wasm32-wasi'?
rustup --version gives:
rustup 1.27.1 (54dd3d00f 2024-04-24)
info: This is the version for the rustup toolchain manager, not the rustc compiler.
info: The currently active `rustc` version is `rustc 1.77.2 (25ef9e3d8 2024-04-09)`
am I doing something wrong?
bjorn3 (May 02 2025 at 11:27):What does rustc -V show? You may be using a stable release from a year ago or so. Try rustup update stable.
Edit: Yeah, rustup says you are using a year old rustc (1.77.2)
stephen (May 02 2025 at 11:37):yea, that fixed it.. maybe the readme should say to have a recent rustup, personally I don't really update it.
stephen (May 02 2025 at 11:40):I also question why the instructions to get wasmtime in the readme are only provided as using the install script. If I'm in the README.md I've likely synced the code and I want to build from source to do development on wastime or cranelift sources contained in the repo.
Ramon Klass (May 02 2025 at 13:25):that readme is for wasmtime-the-application, not wasmtime-the-rust-library, and technically the step that failed for you is "compiling some rust code to wasm" which is out of scope for wasmtime, as it is only concerned with running wasm binaries (and linking, transpiling from wat to wasm etc), but not at all with how to compile rust to wasm
if you're curious, this change has forced you to update your compiler version, it is a very unusual thing to change the names of target triplets but there was a good reason this one time
Last updated: Dec 06 2025 at 05:03 UTC