-
Notifications
You must be signed in to change notification settings - Fork 48
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
Project build issues #103
Comments
the following still works: |
Thank you, it helped me to install istanbul-tools under $GOPATH. However it when I try to use it it does not seem to work properly. $ istanbul --help or this $ istanbul extra encode --config ./config.toml |
Hi @AndriianChestnykh, I'm experiencing that same problem - have you found a solution? |
Setting the build flags worked for me Apparently, this is no longer an issue with go 1.8.1 Reference: |
I had the same issue. The compiled file was in the go binaries.
Adding this line to your bash profile should make them accessible.
Hope this helps the next one looking for a solution! |
I'm still facing an issue in it. I use UBUNTU 16.04. |
There are these errors when trying to build the project with "make" command:
cmd/istanbul/main.go:37: cannot use extra.ExtraCommand (type "github.com/getamis/istanbul-tools/vendor/github.com/urfave/cli".Command) as type "github.com/urfave/cli".Command in array or slice literal
cmd/istanbul/main.go:38: cannot use setup.SetupCommand (type "github.com/getamis/istanbul-tools/vendor/github.com/urfave/cli".Command) as type "github.com/urfave/cli".Command in array or slice literal
cmd/istanbul/main.go:39: cannot use []"github.com/urfave/cli".Command literal (type []"github.com/urfave/cli".Command) as type []"github.com/getamis/istanbul-tools/vendor/github.com/urfave/cli".Command in assignment
make: *** [istanbul] Error 2
The text was updated successfully, but these errors were encountered: