WebAssembly / spec

WebAssembly specification, reference interpreter, and test suite.
https://webassembly.github.io/spec/
Other
3.13k stars 445 forks source link

Install error in OCaml 5.0.0 #1592

Closed liweijian closed 1 year ago

liweijian commented 1 year ago

I'm trying to install wasm via opam, but got error as:

#=== ERROR while compiling wasm.2.0.0 =========================================#
# context     2.1.2 | linux/x86_64 | ocaml-base-compiler.5.0.0 | https://opam.ocaml.org#88824077
# path        ~.opam/5.0.0/.opam-switch/build/wasm.2.0.0
# command     ~.opam/opam-init/hooks/sandbox.sh build make -C interpreter opt unopt
# exit-code   2
# env-file    ~.opam/log/wasm-1437974-3c2639.env
# output-file ~.opam/log/wasm-1437974-3c2639.out
### output ###
# [...]
# make: Entering directory '/home/ci0/.opam/5.0.0/.opam-switch/build/wasm.2.0.0/interpreter'
# echo >_tags "true: bin_annot"
# echo >>_tags "true: debug"
# echo >>_tags "<{util,syntax,binary,text,valid,runtime,exec,script,host,main,tests}/*.cmx>: for-pack(Wasm)"
# ocamlbuild -lexflags -ml -cflags '-w +a-4-27-42-44-45-70 -warn-error +a-3' -I util -I syntax -I binary -I text -I valid -I runtime -I exec -I script -I host -I main -I tests -libs bigarray -quiet main.native
# + /home/ci0/.opam/5.0.0/bin/ocamlopt.opt bigarray.cmxa -g -I util -I binary -I exec -I syntax -I runtime -I host -I main -I script -I text -I valid util/lib.cmx binary/utf8.cmx exec/fxx.cmx exec/f32.cmx exec/f64.cmx exec/ixx.cmx exec/i32.cmx exec/i64.cmx exec/i32_convert.cmx exec/f32_convert.cmx exec/i64_convert.cmx exec/f64_convert.cmx exec/i16.cmx exec/i8.cmx syntax/types.cmx exec/v128.cmx [...]
# File "_none_", line 1:
# Error: Cannot find file bigarray.cmxa
# Command exited with code 2.
# make: *** [Makefile:70: main.native] Error 10
# rm _tags
# make: Leaving directory '/home/ci0/.opam/5.0.0/.opam-switch/build/wasm.2.0.0/interpreter'

<><> Error report <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
┌─ The following actions failed
│ λ build wasm 2.0.0
rossberg commented 1 year ago

Thanks for pointing out, should be fixed now.