Skip to content
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

Closed
gopherbot opened this issue Feb 15, 2013 · 5 comments
Closed

cmd/dist: GOARM auto detection failure #4815

gopherbot opened this issue Feb 15, 2013 · 5 comments
Milestone

Comments

@gopherbot
Copy link

@gopherbot gopherbot commented Feb 15, 2013

by rayneolivetti:

Before filing a bug, please check whether it has been fixed since the
latest release. Search the issue tracker and check that you're running the
latest version of Go:

Run "go version" and compare against
http://golang.org/doc/devel/release.html  If a newer version of Go exists,
install it and retry what you did to reproduce the problem.

Thanks.

What steps will reproduce the problem?
If possible, include a link to a program on play.golang.org.
1. Pull and compile go without specifying GOARM on Arch Linux ARM/Raspberry Pi
2. echo $GOARM
3.

What is the expected output?
6

What do you see instead?
5

Which compiler are you using (5g, 6g, 8g, gccgo)?
5g

Which operating system are you using?
Arch Linux ARM

Which version are you using?  (run 'go version')
go version devel +bae765178262 Mon Feb 11 22:12:56 2013 -0500 linux/arm

Please provide any additional information below.
@minux
Copy link
Member

@minux minux commented Feb 15, 2013

Comment 1:

what's the output of these two commands?
GOARM="" go tool dist env | grep GOARM
go tool dist version
@davecheney
Copy link
Contributor

@davecheney davecheney commented Feb 16, 2013

Comment 2:

I am trying to reproduce this issue now.

Owner changed to @davecheney.

Status changed to Started.

@davecheney
Copy link
Contributor

@davecheney davecheney commented Feb 16, 2013

Comment 3:

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.
@gopherbot
Copy link
Author

@gopherbot gopherbot commented Feb 16, 2013

Comment 5 by rayneolivetti:

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.
@davecheney
Copy link
Contributor

@davecheney davecheney commented Feb 16, 2013

Comment 6:

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.

@rsc rsc added this to the Go1.1 milestone Apr 14, 2015
@rsc rsc removed the go1.1maybe label Apr 14, 2015
@golang golang locked and limited conversation to collaborators Jun 24, 2016
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.