Alright, I got it fixed. I ran go in legacy mode (as *@Anderson Queiroz*
suggested) by manually setting it in the win env var: GO111MODULE=off
(since it's a temp var which resets upon every instance); and reinstalled
Git.
Thanks for the assist guys!
On Wednesday, September 15, 2021 at 3:56:51
Alright, I got it fixed. As Anderson suggested, I ran go in legacy mode by
manually setting GO111MODULE=off in win env var so I doesn't reset upon
next instance of go (since it's a temporary variable). I also reinstalled
git.
Thanks for the assist guys!
On Wednesday, September 15, 2021 at 3:56
If I'm not mistaken `$GOPATH/pkg/mod` where go modules keeps the downloaded
modules, looking up `$GOPATH/pkg/mod` is to look for a module downloaded in
module aware mode and `$GOPATH/src` is for gopath mode.
Are you working with go modules or on the legacy go path mode?
On Tuesday, 14 September
Noted with thanks.
I used "go get ." to download the package "github.com/google/gopacket",
however Go is searching for it in "$GOPATH/src" while it was downloaded to
"$GOPATH/pkg/mod".
*--*
Clitson
On Mon, Sep 13, 2021 at 8:39 PM Ian Lance Taylor wrote:
> On Mon, Sep 13, 2021 at 4:35 PM Clits
On Mon, Sep 13, 2021 at 4:35 PM Clitson Belleau
wrote:
> Hi,
>
> Has anyone had an issue with Go referencing "src" folders from the which
> was changed to "pkg" since v1.6? If so is there any way to fix this or any
> link to a similar issue?
>
> I couldn't find anything in the documentation regar
Hi,
Has anyone had an issue with Go referencing "src" folders from the which
was changed to "pkg" since v1.6? If so is there any way to fix this or any
link to a similar issue?
I couldn't find anything in the documentation regarding this. I am running
the latest v1.17.1 release.
[image: fig1
