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
Since the 4th of May my xgo builds for linux/386 are failing with this message:
Compiling for linux/386...
# runtime/cgo
In file included from _cgo_export.c:3:
/usr/include/stdlib.h:25:10: fatal error: bits/libc-header-start.h: No such file or directory
25 | #include <bits/libc-header-start.h>
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
I'm not very used on tracking down compiling errors so I kindly ask for some help. My little pipeline pulls the latest xgo image for every build and I guess something might have changed here? The commits tell me, that there were changes for arm64. Could that brought some unwanted side effects for 386 builds?
The text was updated successfully, but these errors were encountered:
Thanks @gerricom, while I had tested that PR, it seems that I have missed some testcases, including some relevant to the project I use xgo with (Gitea), and so I am looking into this atm.
I may need to (temporarily) revert the arm PR while I dig through things. Edit: I have done this to give me time while I investigate. The build is building, and the revised image will be available once that is complete.
Since the 4th of May my xgo builds for linux/386 are failing with this message:
I'm not very used on tracking down compiling errors so I kindly ask for some help. My little pipeline pulls the latest xgo image for every build and I guess something might have changed here? The commits tell me, that there were changes for arm64. Could that brought some unwanted side effects for 386 builds?
The text was updated successfully, but these errors were encountered: