Skip to content
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.

Sign up for GitHub

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

Jump to bottom

cmd/go: go install to current directory does not create executable #11065

Closed
phemmer opened this issue Jun 4, 2015 · 2 comments
Closed

cmd/go: go install to current directory does not create executable #11065

phemmer opened this issue Jun 4, 2015 · 2 comments
Labels
FrozenDueToAge
Milestone
Go1.5

Comments

@phemmer
Copy link

phemmer commented Jun 4, 2015

With current master, when I perform GOBIN="$(pwd)" go install, no resulting binary is created. This seems to be a regression from go-1.4.2, specifically as a result of 227fb11.

I use GOBIN="$(pwd)" go install instead of go build as go build does not update the build cache ($GOPATH/pkg). Thus for development, and frequent builds, go install is much faster.

See also #9645
@robpike robpike changed the title go install to current directory does not create executable cmd/go: go install to current directory does not create executable Jun 4, 2015
@robpike robpike added this to the Go1.5 milestone Jun 4, 2015
@robpike
Copy link
Contributor

robpike commented Jun 4, 2015

Almost certainly a consequence of the new removal logic in go build.

@gopherbot
Copy link

CL https://golang.org/cl/11511 mentions this issue.

@rsc rsc closed this as completed in 11a19ae Jul 7, 2015
@golang golang locked and limited conversation to collaborators Jul 11, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge
Projects
None yet
Milestone
Go1.5
Development

No branches or pull requests
3 participants
@phemmer @robpike @gopherbot