-
Notifications
You must be signed in to change notification settings - Fork 26
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 run mage.go build
failed
#286
Comments
Hi @darkforest42, I confirm this. The repo currently requires tinygo 0.31.2. Some changes that I had half backed are needed to make 0.32.0 work, and they are not yet in main |
Hi @M4tteoP, i reinstall tinygo 0.31.2, but build still fail, details are as follows: `panic: runtime error: invalid memory address or nil pointer dereference goroutine 87 [running]: |
My setup is very close to yours (tinygo |
I pushed #287, if you want to give it a go with tinygo |
it does work, thanks |
go version: 1.21.6
tinygo version: 0.32.0
OS: Apple M1
go run mage.go build
failedgithub.com/tetratelabs/proxy-wasm-go-sdk/proxywasm/internal
../../../../../go/pkg/mod/github.com/tetratelabs/[email protected]/proxywasm/internal/hostcall_utils_tinygo.go:31:9: cannot use uintptr(size) (value of type uintpt
r) as int value in struct literal
../../../../../go/pkg/mod/github.com/tetratelabs/[email protected]/proxywasm/internal/hostcall_utils_tinygo.go:32:9: cannot use uintptr(size) (value of type uintpt
r) as int value in struct literal
../../../../../go/pkg/mod/github.com/tetratelabs/[email protected]/proxywasm/internal/hostcall_utils_tinygo.go:39:9: cannot use uintptr(size) (value of type uintpt
r) as int value in struct literal
../../../../../go/pkg/mod/github.com/tetratelabs/[email protected]/proxywasm/internal/hostcall_utils_tinygo.go:40:9: cannot use uintptr(size) (value of type uintpt
r) as int value in struct literal
Error: running "tinygo build -gc=custom -opt=2 -o build/mainraw.wasm -scheduler=none -target=wasi -tags='custommalloc nottinygc_envoy no_fs_access memoize_builders coraza.
rule.multiphase_evaluation'" failed with exit code 1
exit status 1
The text was updated successfully, but these errors were encountered: