Wasmtime GitHub notifications bot (May 15 2020 at 20:07): Wasmtime GitHub notifications bot (May 15 2020 at 20:07):alexcrichton commented on Issue #1715:
In theory this is no longer needed since https://github.com/bytecodealliance/wasmtime/pull/1667, were you testing with an older version of the wasmtime C API though?
Wasmtime GitHub notifications bot (May 15 2020 at 20:39):plicease commented on Issue #1715:
Originally I was trying it will
0.16.0, but I get the same thing with 8f2d442helix% gcc -I/Users/ollisg/opt/wasmtime/dev-8f2d442/include examples/multi.c -L/Users/ollisg/opt/wasmtime/dev-8f2d442/lib -lwasmtime helix% ./a.out Initializing... Compiling module... error: failed to compile module invalid result arity: func type returns multiple values (at offset 41)
Wasmtime GitHub notifications bot (May 15 2020 at 20:51):alexcrichton commented on Issue #1715:
Hm so testing master I can get the panic you reproted in #1716, but I don't get
invalid result arity: func type returns multiple values (at offset 41). Are you sure there wasn't a mixup of which version of wasmtime was installed where?
Wasmtime GitHub notifications bot (May 15 2020 at 20:52):alexcrichton commented on Issue #1715:
(also if you're linking dynamically, are you sure that the library at link-time is also selected at load-time?)
Wasmtime GitHub notifications bot (May 15 2020 at 20:55):plicease commented on Issue #1715:
(also if you're linking dynamically, are you sure that the library at link-time is also selected at load-time?)
Ah yes. I updated the flags to the compiler but forgot to update the dynamic linker path.
Wasmtime GitHub notifications bot (May 16 2020 at 12:56):plicease commented on Issue #1715:
This was my goof, but it would have been easier to diagnose if the version information were available in the dynamic library (and the .h file for C/C++). I'd love to see something implemented for #986
Last updated: Nov 22 2024 at 16:03 UTC