Can't go install ./... this repo #156

Closed
natefinch opened this Issue May 9, 2016 · 1 comment

Comments

Projects
None yet
2 participants

natefinch commented May 9, 2016

My usual first step of looking at a go repo is to go install ./... from the repo root, to make sure everything compiles. But you can't do that with go-systemd, because you get this:

# github.com/coreos/go-systemd/examples/activation
examples/activation/listen.go:25: fixListenPid redeclared in this block
    previous declaration at examples/activation/activation.go:25
examples/activation/listen.go:34: main redeclared in this block
    previous declaration at examples/activation/activation.go:34
examples/activation/udpconn.go:26: fixListenPid redeclared in this block
    previous declaration at examples/activation/listen.go:25
examples/activation/udpconn.go:35: main redeclared in this block
    previous declaration at examples/activation/listen.go:34

Maybe it would be prudent to move each example into their own directory?

Contributor

jonboulle commented May 10, 2016

Mind putting up a patch for this?

Nate Finch notifications@github.com schrieb am Mo., 9. Mai 2016, 17:48:

My usual first step of looking at a go repo is to go install ./... from
the repo root, to make sure everything compiles. But you can't do that with
go-systemd, because you get this:
github.com/coreos/go-systemd/examples/activation

examples/activation/listen.go:25: fixListenPid redeclared in this block
previous declaration at examples/activation/activation.go:25
examples/activation/listen.go:34: main redeclared in this block
previous declaration at examples/activation/activation.go:34
examples/activation/udpconn.go:26: fixListenPid redeclared in this block
previous declaration at examples/activation/listen.go:25
examples/activation/udpconn.go:35: main redeclared in this block
previous declaration at examples/activation/listen.go:34

Maybe it would be prudent to move each example into their own directory?


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#156

@yifan-gu yifan-gu closed this in cf95ff1 May 13, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment