In the middle of a development session, this stupid behavior started and now it looks permanent. I have no idea what happened:
[dtrombley@sleet bin]$ echo $GOROOT
/usr/lib/golang
[dtrombley@sleet bin]$ echo $GOPATH
/home/dtrombley/go/
[dtrombley@sleet bin]$ ./liteide
liteide build error:
../../github.com/Sirupsen/logrus/writer.go:4:2: cannot find package "bufio" in any of:
/home/dtrombley/go/src/bufio (from $GOROOT)
/home/dtrombley/go/src/bufio (from $GOPATH)
What? Why is it using GOPATH in place of GOROOT? This used to work, and mysteriously switched to broken while liteide was running, from one build to the next, literally a few seconds later...
Has anyone seen this? Is there some way I can inspect/set the GOROOT within liteide?
[Edit] Further weirdness: I thought the / at the end of GOPATH might be confusing it, so I removed that. Now:
[dtrombley@sleet bin]$ echo $GOROOT
/usr/lib/golang
[dtrombley@sleet bin]$ echo $GOPATH
/home/dtrombley/go
[dtrombley@sleet bin]$ ./liteide
...
warning: GOPATH set to GOROOT (/home/dtrombley/go) has no effect
../../github.com/Sirupsen/logrus/writer.go:4:2: cannot find package "bufio" in any of:
/home/dtrombley/go/src/bufio (from $GOROOT)
($GOPATH not set)
Misery.