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
I would like to build WASM standalone with access to the file system, but wasmer fails to find imports when using emscripten's env (including failing to import WASI when env symbols are present). Is there a way to get wasmer to handle this or a different tool that can run in this way? I can build these examples to a.js and run with node a.js, but would prefer the STANDALONE_WASM mode.
Failing to find "wasi_snapshot_preview1"."proc_exit" when "env"."__syscall_rmdir" is needed.
The above will also fail if you remove everything but malloc and build with -sALLOW_MEMORY_GROWTH because that references "env"."emscripten_notify_memory_growth".
This demonstrates that we fail to find env symbols even when there are no WASI symbols needed.
$ wasmer --versionwasmer 3.0.0-beta.2
$ emcc --versionemcc (Emscripten gcc/clang-like replacement + linker emulating GNU ld) 3.1.24-git (68a9f990429e0bcfb63b1cde68bad792554350a5)Copyright (C) 2014 the Emscripten authors (see AUTHORS.txt)This is free and open source software under the MIT license.There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I would like to build WASM standalone with access to the file system, but wasmer fails to find imports when using emscripten's
env(including failing to import WASI whenenvsymbols are present). Is there a way to get wasmer to handle this or a different tool that can run in this way? I can build these examples toa.jsand run withnode a.js, but would prefer theSTANDALONE_WASMmode.Failing to find
"wasi_snapshot_preview1"."proc_exit"when"env"."__syscall_rmdir"is needed.The above will also fail if you remove everything but
mallocand build with-sALLOW_MEMORY_GROWTHbecause that references"env"."emscripten_notify_memory_growth".This demonstrates that we fail to find
envsymbols even when there are no WASI symbols needed.Details
Beta Was this translation helpful? Give feedback.
All reactions