I think this ties closely to #32027: we're erroring out because we do not have a module path (and therefore do not have a package path) for package in the working directory.
In theory we could proceed anyway: since the package in the current directory imports only standard-library packages, the only effects of its go.mod file would be to select the go version in use and set accurate debug information, and for most binaries those don't matter much.
What version of Go are you using (
Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (
What did you do?
I have Go 1.12 installed on my system. I cloned the go repo and checked out the tag go1.10.8.
Then i cd'd to the go repo's src directory and ran make.bash
What did you expect to see?
a successful build
What did you see instead?
matloob-macbookpro2:src matloob$ ./make.bash
Building Go cmd/dist using /usr/local/go.
go: cannot determine module path for source directory /Users/matloob/go110 (outside GOPATH, no import comments)
But make.bash does work when GO111MODULE is unset
The text was updated successfully, but these errors were encountered: