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
cmd/dist: GOARM auto detection failure #4815
Labels
Milestone
Comments
I am trying to reproduce this issue now. Owner changed to @davecheney. Status changed to Started. |
I _cannot_ reproduce the issue on rasbian pi@raspberrypi ~/go/src $ hg id 864c37196df8 tip pi@raspberrypi ~/go/src $ uname -a Linux raspberrypi 3.2.27+ #250 PREEMPT Thu Oct 18 19:03:02 BST 2012 armv6l GNU/Linux pi@raspberrypi ~/go/src $ ../pkg/tool/linux_arm/dist env GOROOT="/home/pi/go" GOBIN="/home/pi/go/bin" GOARCH="arm" GOOS="linux" GOHOSTARCH="arm" GOHOSTOS="linux" GOTOOLDIR="/home/pi/go/pkg/tool/linux_arm" GOCHAR="5" GOARM="6" Moving on to archlinuxarm for comparison. |
As I mentioned in the mailing list, the problem actually disappeared when I switched from an old version to a recent version using GOARM=6 explicity. I just tried building everything from scratch without GOARM=6 and it's working fine, and I can't reproduce it either. I am terribly sorry about filing this invalid issue without any real tests. |
Not a problem, there were cases in the past where the auto detection wasn't as reliable. I've just done a test on arch (whatever version they ship form the RPi website + updates) and everything looks to be in order. [root@alarmpi src]# uname -a Linux alarmpi 3.6.11-6-ARCH+ #1 PREEMPT Mon Feb 11 02:33:03 UTC 2013 armv6l GNU/Linux [root@alarmpi src]# ../pkg/tool/linux_arm/dist env GOROOT="/root/go" GOBIN="/root/go/bin" GOARCH="arm" GOOS="linux" GOHOSTARCH="arm" GOHOSTOS="linux" GOTOOLDIR="/root/go/pkg/tool/linux_arm" GOCHAR="5" GOARM="6" [root@alarmpi src]# hg id 86556fe6cad5 tip I'll mark this issue as retracted. Please let me know if it reoccurs. Labels changed: added arch-arm. Status changed to Retracted. |
This issue was closed.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
by rayneolivetti:
The text was updated successfully, but these errors were encountered: