-
Notifications
You must be signed in to change notification settings - Fork 74
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
Cross compilation is not working #42
Comments
I have some fixes for this in #45. |
I too find that none of the following Go versions will work for
The builds with |
Fix problems with travis-ci/gimme#42 and travis-ci/gimme#25
In the end, this fixed it. Since go 1.5, the standard binaries come shipped with cross-compilation support, so the trick is to just download a recent binary, and then set |
@petemoore, I read that as, "The fix for gimme not working is to not use gimme." |
😃 ... so that is my workaround, yes! At least for go 1.5 onwards, where the standard binaries come shipped with cross compilation support. |
Fix problems with travis-ci/gimme#42 and travis-ci/gimme#25
Gimme has broken cross-compilation: travis-ci/gimme#42 Anyway golang now has cross-compilation built-in so we can just use go build with GOOS and GOARCH environment variables. Fixes issue where Travis released a linux binary as a darwin binary for wrench 0.41.0
If this is still happening, could someone affected please report the output of After this bug was filed, some folks did a bunch of work on setting up cross-compilation for the bootstrap binary using |
ASSUMPTION: gimme's bootstrap is not being used to make a Go release which can be copied to another system and used _there_ to build, but is instead invoked locally to build the final version, where the final version will be used for any cross-compilation. Therefore we always want to use the `HOST` variants for OS/ARCH for the bootstrap stage. So, use the new resolution stuff to consider 1.10.x, 1.9.x or 1.8.x for cross-compiling only, where we'll grab the latest on the branch for future cross-compiles rather than continue with something which might have known code-generation bugs. And always go for the ${GIMME_HOSTOS:?}.${GIMME_HOSTARCH:?} variants. Local testing confined to "can install a bootstrap". Might help with issue #42.
ASSUMPTION: gimme's bootstrap is not being used to make a Go release which can be copied to another system and used _there_ to build, but is instead invoked locally to build the final version, where the final version will be used for any cross-compilation. Therefore we always want to use the `HOST` variants for OS/ARCH for the bootstrap stage. So, use the new resolution stuff to consider 1.10.x, 1.9.x or 1.8.x for cross-compiling only, where we'll grab the latest on the branch for future cross-compiles rather than continue with something which might have known code-generation bugs. And always go for the ${GIMME_HOSTOS:?}.${GIMME_HOSTARCH:?} variants. Local testing confined to "can install a bootstrap". Might help with issue #42.
Hi!
I am trying to use gimme cross compilation feature by defining
GIMME_OS
env var.But it seems windows and darwin builds are not affected =(
In the build log of windows branch one could find:
GOOS=linux
moreover, go 1.6 with
GIMME_OS=windows
throws an errorhere's my config file:
build: https://travis-ci.org/mavlyutov/golagraphite/jobs/122741090
The text was updated successfully, but these errors were encountered: