-
Notifications
You must be signed in to change notification settings - Fork 122
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Go 1.11 WebAssembly modules #23
Comments
The fix for this issue is to update to the latest version of wagon ... and then you'll hit go-interpreter/wagon#69 |
Friends, we are still having this issue, even using the updated version of wagon (using @mastersingh24 's fork). Anyone able to use life at the moment? |
I have gotten this working in olin. Relevant commits: Example web assembly module and its output:
More info here. |
Keeping this thread updated: it seems that including most of the standard library brings in syscall/js somehow. This is getting annoying fast. I am going to fork the Go compiler with a custom GOOS ( |
Yay weird linker errors: Xe/go@37bc30e |
can we add issues to the go repo for dagger ?
…On Thu, 6 Sep 2018 at 15:49 Christine Dodrill ***@***.***> wrote:
Yay weird linker errors: ***@***.***
<Xe/go@37bc30e>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#23 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ATuCwoqeNKb98vxksB2xELKgUBhXz3DZks5uYSfigaJpZM4WEJOv>
.
|
@Xe - syscall/js is always included when building for the |
@mastersingh24 could you please update us on the status of this issue? |
@mastersingh24 how much of browser runtime can be pulled into life? |
Can we use something like Otto to replace the JS runtime? |
I have looked into using Otto to replace the JS runtime. I don't feel comfortable doing it because I don't know how much deviation it has from how browser JS does it. |
Hi guys, Any usage of other external communications (i.e. stdin,/stdout, http, sockets, files and etc) will cause your VM to mysteriously fail. |
Any updates with Go 1.12? |
Go 1.12 is actually no better here. |
I got parts of the runtime working in Olin. Here's the code: https://github.com/Xe/olin/tree/master/internal/abi/wasmgo |
Instead of trying to support go's https://hacks.mozilla.org/2019/03/standardizing-wasi-a-webassembly-system-interface/ Relevant issue: golang/go#31105 |
The wasi/wasm target post-dates this issue |
Have you guys done any testing with modules created via Go 1.11? I assume it might likely be an issue with wagon?
Simple test.go:
Using Go 1.11rc1:
GOOS=js GOARCH=wasm go build -o test.wasm test.go
and then
./life -entry main /Users/gsingh/Projects/golang/src/webassembly/test.wasm
with result
Maybe related to go-interpreter/wagon#69 ?
The text was updated successfully, but these errors were encountered: