-
Notifications
You must be signed in to change notification settings - Fork 18k
go/build: does not know about buildmode pkg directories #16378
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
Comments
I expect that cmd/go/build.go needs to update buildContext.InstallSuffix. |
Hmmm, sorry, it already does that. But I guess the problem is that cmd/vet doesn't know about the installsuffix. I see: the |
Thanks, Ian, that was exactly the information I needed to get unstuck. I'll send a CL shortly for preliminary feedback. |
…atforms DO NOT SUBMIT [code freeze] Fixes golang#16378. Change-Id: I99a064f1afec78fb63cb3719061d20be0f21d45d
CL https://golang.org/cl/24930 mentions this issue. |
DO NOT SUBMIT [code freeze] Fixes golang#16378. Change-Id: I99a064f1afec78fb63cb3719061d20be0f21d45d
DO NOT SUBMIT [code freeze] Fixes golang#16378. Change-Id: I99a064f1afec78fb63cb3719061d20be0f21d45d
Create and build/install imp.go:
Then try to use it with
darwin/arm
:Observe that the installed arm packages are in
darwin_arm_shared
, but according to go/build, the PkgObjs are to be found indarwin_arm
.This comes up in practice when attempting to do a cross-platform
go vet
invocation, because vet cannot find thefmt
(and other) packages, which results in a flood of incorrect errors.I'd love help fixing this. I'm not sure what/where the correct fix is, or even who to ask for help. This will shortly block my progress on #11041, so an R=go1.8 CL would be deeply appreciated.
The text was updated successfully, but these errors were encountered: