Skip to content
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

Unabe to install evm #14

Closed
bingen opened this issue Jan 2, 2019 · 6 comments
Closed

Unabe to install evm #14

bingen opened this issue Jan 2, 2019 · 6 comments

Comments

@bingen
Copy link

bingen commented Jan 2, 2019

When trying to install with make (or with go install github.com/CoinCulture/evm-tools/evm) I get the following error:

# github.com/CoinCulture/evm-tools/vendor/github.com/ethereum/go-ethereum/core
vendor/github.com/ethereum/go-ethereum/core/block_validator.go:147:19: not enough arguments in call to set.New
	have ()
	want (set.SetType)

I'm using Debian with Go version 1.11.4

@ebuchman
Copy link
Collaborator

ebuchman commented Jan 3, 2019

Did you run dep ensure first?

@bingen
Copy link
Author

bingen commented Jan 3, 2019

Yes, I did, but I got the following error:

> dep ensure
grouped write of manifest, lock and vendor: failed to export gopkg.in/fatih/set.v0: fatal: failed to unpack tree object 27c40922c40b43fe04554d8223a402af3ea333f3
: exit status 128

Then I found somewhere that dep ensure -update would fix it, so I did that, but I guess not.

@ebuchman
Copy link
Collaborator

ebuchman commented Jan 3, 2019

Is this on a fresh checkout of the repo? Can you try deleting the vendor dir if it exists, or doing a fresh checkout of the repo, and trying again?

@d-xo
Copy link

d-xo commented Jan 4, 2019

I also have the same issue with dep ensure on a fresh checkout of the repo (nixos-19.03).

ebuchman added a commit that referenced this issue Jan 4, 2019
@ebuchman
Copy link
Collaborator

ebuchman commented Jan 4, 2019

My apologies, this was indeed broken. I must have had some cached data. I was able to replicate the issue on a fresh GOPATH. It should work now. Please open a new issue if it still doesn't.

Hopefully implementing #13 will help do away with these issues too.

Thanks for your patience

@bingen
Copy link
Author

bingen commented Jan 5, 2019

Yes, now it woks. Thank you so much!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants