I figured out the source of these reported difference in behaviors.
My win10 system does not have a go.mod file, but my LinuxMint system
does. When I deleted that (and unset GO111MODULE) I was able to compile
on LinuxMint.
So the differences depend on whether there is already a go.mod file i
Robert,
It's probably worth a careful look at
https://github.com/golang/go/wiki/Modules#recent-changes and
https://golang.org/doc/go1.13#modules as well as Marcin's suggestion to run
go env. When I do the latter, I get
GO111MODULE=""
GOPRIVATE=""
(among many other variables but those are probably
I hope this helps. I removed the GO111MODULE=off that I added the other
day to get compilation to work.
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/rob/.cache/go-build"
GOENV="/home/rob/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOP
Could you post the output of "go env" run on linux mint? Maybe there's a
clue in there.
On Mon, Sep 30, 2019 at 9:14 AM Robert Solomon wrote:
> Then my question becomes, what's different about linuxmint 19.2 to require
> me to set GO111MODULE=no
>
> On Mon, Sep 30, 2019, 11:06 AM Everton Marque
Then my question becomes, what's different about linuxmint 19.2 to require
me to set GO111MODULE=no
On Mon, Sep 30, 2019, 11:06 AM Everton Marques
wrote:
> Your code from playground compiled fine for me on Debian Linux.
> Tested with Go 1.13 and 1.13.1.
>
> Just had to include the missing func:
Your code from playground compiled fine for me on Debian Linux.
Tested with Go 1.13 and 1.13.1.
Just had to include the missing func:
func GetUserGroupStr(f os.FileInfo) (string, string) {
return "foo", "bar"
}
Em segunda-feira, 30 de setembro de 2019 11:34:52 UTC-3, Robert Solomon
es
Your experience matches mine when compiled on windows 10.
But linuxmint experience is as I described. Another responder asked me if
it works when I set GO111MODULE=no.
It does work when I do that. I find it interesting that the linux
behavior seems to be different
On Mon, Sep 30, 2019, 9:17
FWIW, I copied your code from Go Playground into ~/go/src/dsrt/dsrt.go on
my OS X machine. I replaced an undefined function at line 375 (see below)
with direct assignments for usernameStr and groupNameStr. It compiled (with
go build) and ran without reporting an error under go 1.13.
// usernam
I guess I was not clear enough. My apologies. dsrt is my own code. I
remember an earlier posting on this list recommended 'go install'
instead of 'go build'
~/go/src/dsrt/dsrt.go, util_linux.go, util_windows.go
And I have written other small programs in go that I use for myself. I
put it i
What was the last version of Go which worked for you?
"dsrt" isn't a valid module path in the new module resolution code. Does it
work if you disable modules - "GO111MODULE=off go install dsrt"?
On Sun, Sep 22, 2019 at 9:56 AM rob wrote:
> Hi. I think I'm having an issue compiling my code w/
Hi. I think I'm having an issue compiling my code w/ go 1.13. I have
not had any issues up until now. I have my code in the default
locations off of ~/go/src w/ a directory for each little bit of code I
wrote.
Running under linuxmint 19.2 amd64, I installed the go binary by first
nuking /u
11 matches
Mail list logo
