After going through a fresh install of go and this package, I get the following after running go build:
../avalanchego/utils/crypto/secp256k1r.go:15:2: cannot find package "github.com/decred/dcrd/dcrec/secp256k1/v3" in any of:
/usr/local/go/src/github.com/decred/dcrd/dcrec/secp256k1/v3 (from $GOROOT)
/Users/doug/go/src/github.com/decred/dcrd/dcrec/secp256k1/v3 (from $GOPATH)
../avalanchego/utils/crypto/secp256k1r.go:13:2: cannot find package "github.com/decred/dcrd/dcrec/secp256k1/v3/ecdsa" in any of:
/usr/local/go/src/github.com/decred/dcrd/dcrec/secp256k1/v3/ecdsa (from $GOROOT)
/Users/doug/go/src/github.com/decred/dcrd/dcrec/secp256k1/v3/ecdsa (from $GOPATH)
../../spf13/viper/internal/encoding/hcl/codec.go:8:2: cannot find package "github.com/hashicorp/hcl/hcl/printer" in any of:
/usr/local/go/src/github.com/hashicorp/hcl/hcl/printer (from $GOROOT)
/Users/doug/go/src/github.com/hashicorp/hcl/hcl/printer (from $GOPATH)
The first two can be resolved by changing the following lines in ava-labs/avalanchego/utils/crypto/secp256k1r.go:
"github.com/decred/dcrd/dcrec/secp256k1/v3/ecdsa" to "github.com/decred/dcrd/dcrec/secp256k1/ecdsa"secp256k1 "github.com/decred/dcrd/dcrec/secp256k1/v3" to secp256k1 "github.com/decred/dcrd/dcrec/secp256k1"
Output from ls in ~/go/src/github.com/decred/dcrd/dcrec/secp256k1:
After going through a fresh install of go and this package, I get the following after running
go build
:The first two can be resolved by changing the following lines in
ava-labs/avalanchego/utils/crypto/secp256k1r.go
:"github.com/decred/dcrd/dcrec/secp256k1/v3/ecdsa"
to"github.com/decred/dcrd/dcrec/secp256k1/ecdsa"
secp256k1 "github.com/decred/dcrd/dcrec/secp256k1/v3"
tosecp256k1 "github.com/decred/dcrd/dcrec/secp256k1"
Output from ls in
~/go/src/github.com/decred/dcrd/dcrec/secp256k1
:I'm not sure how to resolve the last one, as I'm not familiar with the package. But it seems its directory structure has been altered.
Output from ls in
~/go/src/github.com/hashicorp/hcl
:My go version:
I'm unsure whether this is an isolated issue with just my environment, but considering I just did a fresh install of go, I doubt it.