-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
update to new cross toolchain #2037
Conversation
Signed-off-by: Tonis Tiigi <tonistiigi@gmail.com>
Signed-off-by: Tonis Tiigi <tonistiigi@gmail.com>
Signed-off-by: Tonis Tiigi <tonistiigi@gmail.com>
FROM gostable AS go-linux | ||
FROM golatest AS go-darwin | ||
FROM golatest AS go-windows-amd64 | ||
FROM golatest AS go-windows-386 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want to support windows 386?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I only left amd64&arm64 in the CI. These are just to cover all possible options. Once we don't need to switch between go versions this can be all removed.
# xx is a helper for cross-compilation | ||
FROM --platform=$BUILDPLATFORM tonistiigi/xx:golang@sha256:810dc54d5144f133a218e88e319184bf8b9ce01d37d46ddb37573e90decd9eef AS xx | ||
|
||
FROM --platform=$BUILDPLATFORM golang:1.13-alpine AS gostable |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(Can be another PR, but we seriously need to move away from Go 1.13)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tiborvass has a spreadsheet with all the possible EINTR
for syscalls handlers for go1.13+ that needs to be confirmed to not have possible unfixed cases. @tiborvass please share with @AkihiroSuda
But yes, unrelated to this PR.
@AkihiroSuda @crazy-max