You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Trying to build nitro outside of docker fails.
Using nitro at tag v3.2.1
To Reproduce
Steps to reproduce the behavior:
Start from a modern system
Downgrade libraries as required: nodejs 18 (anything more will cause hardhat to fail) and go 1.22 (go 1.23 cause failure)
run make or make all
See error
target/bin/prover target/machines/latest/replay.wasm --generate-binaries target/machines/latest \
-l target/machines/latest/forward.wasm -l target/machines/latest/soft-float.wasm -l target/machines/latest/wasi_stub.wasm -l target/machines/latest/host_io.wasm -l target/machines/latest/user_host.wasm -l target/machines/latest/arbcompress.wasm -l target/machines/latest/program_exec.wasm
Error: failed to validate WASM binary at "target/machines/latest/wasi_stub.wasm"
Caused by:
0: failed to validate target/machines/latest/wasi_stub.wasm
1: reference-types not enabled: zero byte expected (at offset 0x18c3)
Location:
prover/src/binary.rs:329:10
Expected behavior
There are no clear building instructions, but this error seems to happen maybe because the wasm code is generated using a recent version of rust (rust 1.83.0 with wasi sdk 25)
Additional context
I've tried running the various make operations done in Dockerfile, but this fails also with the same error
The text was updated successfully, but these errors were encountered:
Describe the bug
Trying to build nitro outside of docker fails.
Using nitro at tag v3.2.1
To Reproduce
Steps to reproduce the behavior:
Expected behavior
There are no clear building instructions, but this error seems to happen maybe because the wasm code is generated using a recent version of rust (rust 1.83.0 with wasi sdk 25)
Additional context
I've tried running the various make operations done in Dockerfile, but this fails also with the same error
The text was updated successfully, but these errors were encountered: