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: new Go tools like cmd/new5a should go into tool directory, not go/bin #9708

Closed
4ad opened this issue Jan 28, 2015 · 2 comments
Closed

cmd/go: new Go tools like cmd/new5a should go into tool directory, not go/bin #9708

4ad opened this issue Jan 28, 2015 · 2 comments
Labels
FrozenDueToAge

Comments

@4ad
Copy link
Member

4ad commented Jan 28, 2015

cmd/dist will put them in the tool directory, but go install cmd/new5a will put it in go/bin, making for fun debugging sessions when using go tool new5a.

We should decide what's the best place for the new tools, and use it consistently.
@4ad 4ad added bug labels Jan 28, 2015
@4ad
Copy link
Member Author

4ad commented Jan 28, 2015

Also, liblink will always invoke the objwriter in tool, not bin.

@4ad
Copy link
Member Author

4ad commented Jan 28, 2015

Nevermind, user error. cmd/go knows to do the right thing already, but apparently I had a stale go tool.

@4ad 4ad closed this as completed Jan 28, 2015
@golang golang locked and limited conversation to collaborators Jun 25, 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
No milestone
Development

No branches or pull requests
2 participants
@4ad @gopherbot