-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
could not import fmt #105
Comments
Looks like something is wrong with GOPATH/GOROOT. What is an output of |
[aoneill@foolxps blah]$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/aoneill/.cache/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/aoneill"
GOPROXY=""
GORACE=""
GOROOT="/home/aoneill/go-tip"
GOTMPDIR=""
GOTOOLDIR="/home/aoneill/go-tip/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build401827573=/tmp/go-build -gno-record-gcc-switches"
[aoneill@foolxps blah]$ go version
go version go1.11 linux/amd64
[aoneill@foolxps blah]$ proteus --version
proteus version 1.0.0 |
The setup is a bit unusual (GOROOT inside GOPATH). It might force proteus to think that package |
I moved my GOPATH ~/workspace and kept GOROOT ~/go-tip. That fixed it. It seems strange to me since I've been using this set up for years. Should proteus only search $GOPATH/{src,pkg}? |
It looks like a bug in https://github.com/src-d/go-parse-utils, since it has a custom import resolver. Filed an issue there: src-d/go-parse-utils#13 |
I'm getting an error when I run proteus on a very basic example package.
the blah package just includes
any idea what is going on here?
The text was updated successfully, but these errors were encountered: