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
cmd/go2go: build fails to recognize imports that should be resolved relatively (but not always) #39766
Comments
It seems like |
The go2go tool does not support modules. Have you set the |
I had not. I moved to a GO2PATH directory structure and I see less errors, but I'm still getting |
Can you provide exact instructions showing how we can reproduce the problem? The go-iter package builds successfully for me. |
I was working on a branch, which is why I added I created #39797 with a more complete description of the error mode and a reproduction. I'm not sure if |
If I have a directory that contains a
go.mod
file that defines the directory asmodule gitlab.com/firelizzard/go-iter
, and in a subdirectory./assert
I importiter "gitlab.com/firelizzard/go-iter"
,go tool go2go build
should recognize thatiter
should be resolved relatively, and should successfully build. However, it instead attempts to fetchiter
. Other times, I have been able to make this work, but I don't know why it worked then (nor do I have an example of it working).What version of Go are you using (
go version
)?What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
git clone https://gitlab.com/firelizzard/go-iter -b assert-pkg
cd go-iter/assert
go tool go2go build
What did you expect to see?
A successful build
What did you see instead?
The text was updated successfully, but these errors were encountered: