Try dropping the 'main', unless it's really the intended import path of the package you want to run tests on.
You will have to provide more details like output of `go env`files in ~/go/src/jennyemily2/src/main and at least theirpackage clause and imports. What does go build -v do?
--
You received this message because you are subscribed to a topic in the Google Groups "golang-nuts" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/golang-nuts/ubYw0OQXLvA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to golang-nuts...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Indeed, I changed the 'main' directory to 'golangtest' and did the same for the package statements in both .go files, and everything worked.I had somehow got the impression that the main program had to be in package main; I am not sure why.The golang documentation should be updated to say that one cannot use 'main' as a package name, and there should be an error message if one does.
On Wed, May 6, 2015 at 10:58 PM, Martin Ellison <m...@acm.org> wrote:Indeed, I changed the 'main' directory to 'golangtest' and did the same for the package statements in both .go files, and everything worked.I had somehow got the impression that the main program had to be in package main; I am not sure why.The golang documentation should be updated to say that one cannot use 'main' as a package name, and there should be an error message if one does.It does seem like a bug of the go tool, although a minor one.