use the host's GOEXE when building the linker
We're building the linker binary for the host GOOS, not the target GOOS that we happen to be building for. I noticed that, after running `go test`, my garble cache would contain both link and link.exe, which made no sense as I run linux and not windows. `go env` has GOHOSTOS to mirror GOOS, but there is no GOHOSTEXE to mirror GOEXE, so we reconstruct it from runtime.GOOS, which is equivalent to GOHOSTOS. Add a regression test as well.pull/703/head
parent
b87830eb97
commit
cf49f7f3b1
Loading…
Reference in New Issue