-
Notifications
You must be signed in to change notification settings - Fork 80
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
Windows build failure: undefined reference to `_setjmp' #192
Comments
I've confirmed that downgrading to mingw 11.2.0 fixes the issue. sqlc-dev/sqlc#2757 |
My guess is that MinGW changed ABIs of the |
Unfortunately v13 seems to have the same issue: example failed run. |
CI for this repository is failing with the same issues as above. Interestingly though they're also failing with
It looks like the 13.0.0 release happened right at the time the github runner upgrade was rolling out, so the CI passed here but has failed ever since. I don't know what's going on with The 13.0.0 artifacts for Wasmtime itself were produced on an older version of the github runner (I think). The |
This might be related: golang/go#57455 (comment) |
According to #194 and the linked Go issues I've deduced:
So @kyleconroy I think your issue is indeed to keep MinGW toolchains in sync, and my issue is to do that and upgrade Go. As to the technical matter at hand I didn't realize that |
The latest release looks like it fixed this issue (successful build without workaround). Nice! |
I build wasmtime-go using Github Actions. The latest release of their Windows runner upgraded mingw-w64 from 11.2.0 to 12.2.0 and it appears to have broken things.
https://github.com/actions/runner-images/releases/tag/win22%2F20230918.1
Full logs are available here
The text was updated successfully, but these errors were encountered: