ConfigureWebAssembly1.13.3 #37628
Comments
|
How did you produce the .wasm file? Did you follow the steps at https://golang.org/wiki/WebAssembly#getting-started or something else? Which version of |
dmitshur
added
the
WaitingForInfo
|
WASM_EXEC.JS vERSION i DON'T KNOW. However I FOLLOW ALL STEPS STEPS COPY
BECAUSE IT THROW ERROR cp. So I copy from github. When i run command it
produce wasm file. However I already in my go directory
This Message send through secure channel called BBM
…On Tue, Mar 3, 2020 at 8:25 PM Dmitri Shuralyov ***@***.***> wrote:
How did you produce the .wasm file? Did you follow the steps at
https://golang.org/wiki/WebAssembly#getting-started or something else?
Which version of wasm_exec.js file are you using?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#37628?email_source=notifications&email_token=AE45QD47U7564PAT367DE3LRFUOOTA5CNFSM4LAKHOIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENT5PHI#issuecomment-594007965>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AE45QD46PD4B3DY64BDF3O3RFUOOTANCNFSM4LAKHOIA>
.
|
If you copied it from GitHub, you might have gotten the version from Go 1.14. In your original issue report, you said you were using Go 1.13.3. If that's the case, that could explain the problem you're seeing. You should ensure you're using a matching version of the Go compiler and the If you're looking to get help or have more questions about this, I recommend the resources listed at https://golang.org/wiki/Questions. They are better suited for asking questions. We use the issue tracker for tracking bugs in the Go project, so fewer people will be able to answer questions here. |
|
how to check version wasm_exec.js
This Message send through secure channel called BBM
…On Tue, Mar 3, 2020 at 11:05 PM Dmitri Shuralyov ***@***.***> wrote:
So I copy from github.
If you copied it from GitHub, you might have gotten the version from Go
1.14. In your original issue report, you said you were using Go 1.13.3. If
that's the case, that could explain the problem you're seeing.
You should ensure you're using a matching version of the Go compiler and
the wasm_exec.js.
If you're looking to get help or have more questions about this, I
recommend the resources listed at https://golang.org/wiki/Questions. They
are better suited for asking questions. We use the issue tracker for
tracking bugs in the Go project, so fewer people will be able to answer
questions here.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#37628?email_source=notifications&email_token=AE45QDYB3LH7G5QMBHFUWZ3RFVBGTA5CNFSM4LAKHOIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENUQ5IY#issuecomment-594087587>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AE45QDZZCITE3BUNQLA7VYTRFVBGTANCNFSM4LAKHOIA>
.
|
|
The version of wasm_exec.js is tied to the Go repo version. If you are taking wasm_exec.js from Github, you likely have taken from the master branch. That will not be compatible with your installed Go distribution, which is Go 1.13.3. To get the right wasm_exec.js, you need to get it from I will close this issue now since this is not a bug. If you still have problems, please feel free to ask your question in any of the forums below:
Thanks |
What version of Go are you using (
go version)?Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (
go env)?amd64
go envOutputWhat did you do?
What did you expect to see?
Hello Assembly on my console
What did you see instead?
LinkError: "import object field 'runtime.nanotime' is not a Function"
The text was updated successfully, but these errors were encountered: