-
Notifications
You must be signed in to change notification settings - Fork 18k
misc/dist: go1.2.freebsd/amd64 binary distribution segfaults on FreeBSD 9.2 x86-64 #7025
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
Labels
Comments
This is the build from https://go.googlecode.com/files/go1.2.freebsd-amd64.tar.gz. I also built lang/go from ports. |
Ahh ok I understand now. Please make the following changes to your setup and try again 1. move the files from https://go.googlecode.com/files/go1.2.freebsd-amd64.tar.gz to /usr/local/go as described in the install documentation 2. ensure that /usr/local/go/bin is in your PATH and no other versions of go are in your path 3. ensure that GOROOT is not set. If none of these steps resolves the problems, please reverse these steps and remove any trace of Go from your system before attempting to build from source. Specifically _do_not_set_ GOROOT. Labels changed: added repo-main, os-freebsd. |
@astrange, I cannot reproduce this problem using the version of Go 1.2 from the download site. In addition to my comments in #3 please check that you have installed go from the download site correctly, your original issue report included this line 0x0000000000476dc7 in runtime.sysctl () at /usr/local/go/src/pkg/runtime/sys_freebsd_amd64.s:289 289 /usr/local/go/src/pkg/runtime/sys_freebsd_amd64.s: No such file or directory. which suggested that /usr/local/go/src/pkg/runtime/sys_freebsd_amd64.s was missing. If this were the case then you may not have installed the binary Go installation correctly. |
This is https://golang.org/issue/7056. |
Status changed to Duplicate. Merged into issue #7056. |
This issue was closed.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
by astrange:
The text was updated successfully, but these errors were encountered: