Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Why "go build" depends on $GOROOT/src/pkg #4635
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
issue #2775, more or less... |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
davecheney
Jan 9, 2013
Contributor
The go tool currently requires the source to be present, even if the compiled package is present. There is a workaround, if you leave an empty directory, _with_ an mtime older than the compiled package, in src/ then the go tool _should_ work.
Status changed to Duplicate.
Merged into issue #2775.
The go tool currently requires the source to be present, even if the compiled package is present. There is a workaround, if you leave an empty directory, _with_ an mtime older than the compiled package, in src/ then the go tool _should_ work. Status changed to Duplicate. Merged into issue #2775. |
gopherbot
added
duplicate
labels
Jan 9, 2013
rsc
added this to the Go1.1 milestone
Apr 14, 2015
rsc
removed
the
go1.1
label
Apr 14, 2015
gopherbot
locked and limited conversation to collaborators
Jun 24, 2016
gopherbot
added
the
FrozenDueToAge
label
Jun 24, 2016
This issue was closed.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
gopherbot commentedJan 9, 2013
by xuxinhua1984: