cmd/go: command with file with wrong package silently fails to build #3389
Labels
Milestone
Comments
|
Labels changed: added priority-go1, removed priority-triage. Owner changed to @rsc. Status changed to Accepted. |
In issue #3390 I asked: "Just to check, is it okay to use stuff under cmd? e.g. src/cmd/foo? Or is the whole cmd/* reserved? If it is, an error might be better than having it mostly work." Based on Russ's comment here, it seems the answer is that cmd/* is reserved if you are in a GOROOT project. Maybe the go tool shouldn't build anything under any GOPATH's src/cmd directory then? I can see other people making the same mistake as we have. src/pkg sorted itself out, because there your import path would be pkg/foo, which no-one wants. |
Silent was the wrong word. The confusing thing was that this doesn't work: $ rm -rf bin pkg; GOPATH=`pwd` go install -v cmd/bar can't load package: package cmd/bar: open /path/to/go/src/cmd/bar: no such file or directory but this does work: $ rm -rf bin pkg; GOPATH=`pwd` go install -v cmd/foo/bar It's much less confusing when you know that cmd/* is kind of reserved and that cmd/*/* is "less" reserved. |
|
This issue was closed by revision 8b6534b. Status changed to Fixed. |
alberts
added
fixed
Suggested
This issue was closed.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What steps will reproduce the problem? tree: src/cmd/bar/bork.go src/cmd/bar/main.go $ cat src/cmd/bar/bork.go package bork $ cat src/cmd/bar/main.go package main func main() {} What is the expected output? some kind of build error What do you see instead? $ rm -rf bin pkg; GOPATH=`pwd` go install -v ./... warning: "./..." matched no packages $ rm -rf bin pkg; GOPATH=`pwd` go install -v cmd/bar can't load package: package cmd/bar: open /path/to/go/src/cmd/bar: no such file or directory Which compiler are you using (5g, 6g, 8g, gccgo)? 6g Which operating system are you using? linux Which revision are you using? (hg identify) go version weekly.2012-03-22 +ee5c7588cb7f Please provide any additional information below. I encountered this error while moving some package code into a command to reduce the code for another bug report. I forgot to update all the package lines, and my command "disappeared".The text was updated successfully, but these errors were encountered: