You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While using Go 1.4 as the bootstrap compiler: GOOS=linux GOARCH=arm64 ./make.bash
What did you expect to see?
Logs from a successful cross-compilation.
What did you see instead?
Before the successful cross-compilation, the following scary-sounding warning: 2020/09/21 09:05:27 unsupported GOARCH arm64
This output comes from make.bash invoking go version on the bootstrap compiler with the GOOS and GOARCH provided by the user. Since I'm using 1.4 as a bootstrap and it didn't support GOARCH=arm64 (or many other GOARCHes), the bootstrap compiler complains.
It looks like this was introduced in CL 204757 as a simple debugging aid to print the bootstrap compiler's version in the make.bash log. Probably the simplest thing to do is just clear GOOS and GOARCH on the go version invocation.
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes. And with Go 1.14 (but not Go 1.13)
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
While using Go 1.4 as the bootstrap compiler:
GOOS=linux GOARCH=arm64 ./make.bash
What did you expect to see?
Logs from a successful cross-compilation.
What did you see instead?
Before the successful cross-compilation, the following scary-sounding warning:
2020/09/21 09:05:27 unsupported GOARCH arm64
This output comes from make.bash invoking
go version
on the bootstrap compiler with the GOOS and GOARCH provided by the user. Since I'm using 1.4 as a bootstrap and it didn't support GOARCH=arm64 (or many other GOARCHes), the bootstrap compiler complains.It looks like this was introduced in CL 204757 as a simple debugging aid to print the bootstrap compiler's version in the make.bash log. Probably the simplest thing to do is just clear GOOS and GOARCH on the
go version
invocation./cc @bradfitz @ianlancetaylor
The text was updated successfully, but these errors were encountered: