Closed dsx12 closed 5 years ago
Your GOPATH might not be in your PATH. Try adding your GOPATH to the PATH variable in your bashrc, and sourcing your bashrc to load the changes. Then you should be able to call gscript anywhere
admin@kali ~$ echo $GOPATH /home/admin/dev/go:
?
this is what's in my .bashrc: " export GOPATH=/home/admin/go-workspace export GOROOT=/usr/local/go export PATH=$GOPATH/bin:$PATH export PATH=$PATH:$GOPATH/bin export GOROOT="/usr/lib/go" " locations: " /usr/bin/go /usr/lib/go /usr/local/go /usr/share/go /usr/local/go/bin/go /usr/share/man/man1/go.1.gz "
This is not a gscript build issue, it's a basic golang usage issue. I just ran go get github.com/gen0cide/gscript/cmd/gscript
on a linux/amd64 system w/ go1.10.3 and it properly builds and added the gscript binary to $GOPATH/bin/gscript
As a systems test, can you go get other binaries and do they work properly?
I followed every step but for some reason after building there is no ./gscript file compiled?
when I run ./gscript I receive:
"bash: gscript: command not found"
any ideas?