Can you try using the 64-bit compiler to make a 32-bit binary? Set the GOARCH environment variable to 386 before invoking go build.

Marking as Go1.8 since this is not a regression in 1.7.

Also, can you please provide the complete output of the "go env" as the template requests? (Assuming that doesn't itself crash.) Thanks.

SOLUTION

env GOARCH=386 \go\bin\go.exe build or env GOARCH=386 go build

I tested by recompiling a database app with and without the env GOARCH=386 prefix. (Again, note that I need 32-bit app so it could connect to legacy database). It worked with the prefix! I was able to query the database (an old IBM product... we're migrating next year).

Thanks for the tip, @quentinmit.

Here's the env info too.

set GOARCH=amd64
set GOBIN=
set GOEXE=.exe
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=
set GORACE=
set GOROOT=c:\go
set GOTOOLDIR=c:\go\pkg\tool\windows_amd64
set GO15VENDOREXPERIMENT=1
set CC=gcc
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0
set CXX=g++
set CGO_ENABLED=1

Closing issue

I'm glad the workaround worked for you, but we'd still like to find out if there is something wrong with the 386 Go binaries. Can you see if the 1.7rc6 386 binaries also crash on your machine?

What version of Windows are you using? I could not reproduce it on my Windows 10.

I'll test if 1.7rc6 works.

Running on Windows 7 Enterprise (64-bit).

Plot thickens...

I downloaded 1.7rc6 386 binaries and attempted to compile a couple programs (both simple and complex). Here' s error message:

go tool: no such tool "compile"

Hope this helps.

I suspect that $GOROOT doesn't match newly installed location.
Can you check output of go env is correct? If no, please set environmental variable manually, then retry it.

"I suspect that $GOROOT doesn't match newly installed location."

As previously stated, I do not have admin rights on this computer, thus am unable to set system environments (aside from an annoying %go% user environment variable). There is a workaround (see above) for compiling to 32-bit from another version.

I use binaries on this computer, thus building via /go/bin/go.exe build. This works in all other circumstances (e.g. 1.6.3 windows 64-bit), except for 386 compilers somewhere after version 1.3~. So, if $GOROOT value is the issue, it's only an issue for 386 versions after version 1.3~.

Please see above for go env output.

Your go env is strange. If you use 386 version of Go, $GOARCH should be 386.
Are you sure you are using downloaded binary?

That's probably the output from the 64-bit binary (original issue was with 386; I'll change above comment when I have a chance). Since I'm using binaries, GOARCH willl be whatever default is... For example, the binary for 1.7rc6 386 is GOARCH=386.

Did you extract zip file to C:\Go?

Yes, extracted from zip.

Are you using an unix-like shell?

(I can't see env command on my cmd.exe)

env works fine on both terminal apps I use (including cmd.exe)

Hmm, does $GOTOOLDIR exist on filesystem? (e.g "C:\Go\pkg\tool\windows_386")

Yep, that folder exists

can you invoke compile.exe x.go in that directory? (x.go is your source code)

@hirochachacha, are you able to replicate the error messages?

I can replicate go tool: no such tool "compile" by setting wrong $GOROOT.

I cannot replicate go build command-line-arguments: c:\go\pkg\tool\windows_386\compile.exe: exit status 1073741855. I want to know that If you run compile.exe directly on Go 1.7, you will get same error as on Go 1.6.3.

Because two error messages indicate different issue.