You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've historically checked out my Go development trees to $HOME/go. (where it naturally falls if you do git clone https://go.googlesource.com/go without an additional argument)
That habit predates the new automatic GOPATH value of $HOME/go.
But that led to this surprising behavior on a new machine I was benchmarking:
I've historically checked out my Go development trees to $HOME/go. (where it naturally falls if you do
git clone https://go.googlesource.com/go
without an additional argument)That habit predates the new automatic GOPATH value of $HOME/go.
But that led to this surprising behavior on a new machine I was benchmarking:
In $HOME/go ...
Here's
$HOME/go/bin/go
'sversion
command showing that I just built Go...And can run
go env
from$HOME/go
too....But if I cd down into
src
(which contains ago.mod
file), I can't use the same go binary anymore to rungo env
(or rungo tool dist test
, etc):Is this working as intended?
Can it be made more helpful if I'm holding it wrong?
/cc @bcmills
The text was updated successfully, but these errors were encountered: