-
Notifications
You must be signed in to change notification settings - Fork 17.5k
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
doc: go1.10.html states that i386/amd64 executables fail on NetBSD amd64 #23073
Comments
The typo was already fixed in 38083c8 So does this pass now on an amd64 NetBSD kernel:
? Is there a pullup to the netbsd-8 branch pending? |
@krytarowski, you didn't set
So it's auto-detecting that your host architecture is amd64 and the compiler/linker are 64-bit, even if it's producing 32-bit binaries in the end. |
http://netbsd.org/~kamil/golang/golang-i386-on-amd64-2017-12-11-hosti386.txt NetBSD-8 will receive the needed patches. |
Thanks. Feel free to review https://golang.org/cl/82918 |
Change https://golang.org/cl/82918 mentions this issue: |
|
The arm port is known to work, but I don't know offhand the status. |
|
If we haven't had a builder for it for years, we assume it doesn't work. |
I will give it a try tomorrow on RPi1. |
https://releng.netbsd.org/cgi-bin/req-8.cgi tickets 443 and 444 |
I've fired building go14 (with dependencies) natively on: armv6-unknown-netbsdelf*-eabihf It will take a while. |
@krytarowski, there's no need for that. Your GOROOT_BOOTSTRAP environment variable defaults to $HOME/go1.4 but that's just a default, and it doesn't need to be Go 1.4. It can be anything greater than that, too. So you can use a fast machine to run master's $GOROOT/src/bootstrap.bash and set GOOS=netbsd GOARM=arm and build your $GOROOT_BOOTSTRAP from the fast machine. |
I don't have enough RAM, and I don't want to use swap on this device. I will ask other developers with more advanced ARM hardware for a test. |
OK, upstream golang/arm is broken - it works with floating patches. Part of them are in https://github.com/oshimaya/go/commits/go1.4-netbsd |
Okay, then I can update the docs to say that netbsd/arm is definitely broken, unless you want to mail those patches soon. |
I cannot fix it myself in close time, as I'm burdened by amd64 work. |
Change https://golang.org/cl/83856 mentions this issue: |
Remove the ambiguity, know that we know it's actually broken, per #23073 (comment) Updates #23073 Change-Id: I9b904da2f4c7105a0727d2a9056aaa6895d3dadc Reviewed-on: https://go-review.googlesource.com/83856 Reviewed-by: Ian Lance Taylor <iant@golang.org>
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version
)?N/A
Does this issue reproduce with the latest release?
N/A
What operating system and processor architecture are you using (
go env
)?N/A
What did you do?
N/A
What did you expect to see?
Removed note that 32-bit applications are broken on 64-bit NetBSD kernel.
What did you see instead?
The reverse.
The breakage was a regression on HEAD.
Fix:
http://mail-index.netbsd.org/source-changes/2017/12/07/msg090270.html
The text was updated successfully, but these errors were encountered: