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 
escreveu:
>
> 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 AM Michael Ellis <michae...@gmail.com 
> <javascript:>> wrote:
>
>> 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.
>>
>> // usernameStr, groupnameStr := GetUserGroupStr(f) // util function in 
>> platform specific code, only for linux and windows.  Not needed anymore.  
>> Probably won't compile for foreign computer.
>>                         // GetUserGroupStr() is undefined, so hardcode a 
>> couple of nonsense strings to test compilation.
>> usernameStr := "foo"
>> groupnameStr := "bar"
>>
>>
>>
>> On Saturday, September 28, 2019 at 2:55:51 PM UTC-4, rob wrote:
>>>
>>> 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 in https://play.golang.org/p/U7FgzpqCh-B
>>>
>>> It compiles and runs fine on go 1.12.x under linux, and fine on go 1.13 
>>> under windows 10.  I have not yet installed go1.13.1 on my windows 10 box.
>>>
>>> I remember a promise that anything that compiles under go 1.0.0 will not 
>>> be broken.  Not being able to compile using go 1.13 that works fine using 
>>> go 1.12.x, broke my code.
>>>
>>> I'm not a professional programmer.  I don't know what else to include 
>>> here to demonstrate my problem.
>>>
>>> Thanks for your response.
>>>
>>> --rob solomon
>>>
>>>
>>>
>>> On 9/28/19 11:42 AM, Marcin Romaszewicz wrote:
>>>
>>> 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 <drro...@fastmail.com> wrote:
>>>
>>>> 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 /usr/local/go, and then
>>>>
>>>>      sudo tar -C /usr/local -xf go1.13.linux-amd64.tar.gz.
>>>>
>>>> When I run go version, I get go version go1.13 linux/amd64
>>>>
>>>> Now when I run
>>>>
>>>>      go install dsrt
>>>>
>>>> I'm getting an error message:
>>>>
>>>>      can't load package: package dsrt: mallformed module path "dsrt" : 
>>>> missing dot in first path element.
>>>>
>>>> I do not have, need or use a go.mod.  In fact, I don't really 
>>>> understand 
>>>> them.  And I don't yet understand what vendoring means.
>>>>
>>>> As an aside, I also compile on a win10 amd64 computer.  I installed 
>>>> windows binary in the usual way on that computer, compiled my code 
>>>> using 
>>>> go install, and I've not had any issues there.  I only have an issue 
>>>> here on linuxmint and go 1.13.
>>>>
>>>> What's up?
>>>>
>>>> --rob solomon
>>>>
>>>>
>>>> -- 
>>>> You received this message because you are subscribed to the Google 
>>>> Groups "golang-nuts" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>> an email to golan...@googlegroups.com.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/golang-nuts/3e9c5dad-2fda-9574-d8f9-8cedfb7986e5%40fastmail.com
>>>> .
>>>>
>>> -- 
>>> You received this message because you are subscribed to a topic in the 
>>> Google Groups "golang-nuts" group.
>>> To unsubscribe from this topic, visit 
>>> https://groups.google.com/d/topic/golang-nuts/5hh--qle2KI/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to 
>>> golan...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/golang-nuts/CA%2Bv29LtsWqufQHw%2BmJtAe60KnCHPag9SPVAtjkP2XzkkuHcwyg%40mail.gmail.com
>>>  
>>> <https://groups.google.com/d/msgid/golang-nuts/CA%2Bv29LtsWqufQHw%2BmJtAe60KnCHPag9SPVAtjkP2XzkkuHcwyg%40mail.gmail.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "golang-nuts" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/golang-nuts/5hh--qle2KI/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> golan...@googlegroups.com <javascript:>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/golang-nuts/84d7a41b-5fff-428c-9e10-244ae2cc6a0b%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/golang-nuts/84d7a41b-5fff-428c-9e10-244ae2cc6a0b%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/9e61ee25-b953-4947-8134-b3f054d8bb69%40googlegroups.com.

Reply via email to