-
Notifications
You must be signed in to change notification settings - Fork 18k
cmd/tool/compile: go build
cannot generate executable file
#55853
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
Comments
That's true, but i think it should print errors instead of generate the executable. |
Good idea. Should the standard library or any package in go/src be considered a module? |
Yes, and should throw the error that package name is duplicated. |
Change https://go.dev/cl/434095 mentions this issue: |
Duplicate of #35270 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
I create following files under folder image:
file1: go.mod
file2:
Then I run
go build
, then no any error reported, andecho $?
outputs 0. That saidgo build
success, but no any executable generated.What did you expect to see?
I think it should generate the executable.
What did you see instead?
No executable generated. Go compiler doesn't differentiate go inner image package and user-defined image module? If I rename module image to xxx/image, it works as expected.
The text was updated successfully, but these errors were encountered: