Closed GoogleCodeExporter closed 9 years ago
It doesn't *say* anything but that doesn't mean it's not *doing* anything.
Look inside the $GOPATH/bin directory.
Original comment by a...@golang.org
on 13 Jul 2012 at 6:00
nothing is there
$ ls -al ~/.golib/
total 0
drwxr-xr-x 2 gerad staff 68 Jul 13 06:36 .
drwxr-xr-x+ 73 gerad staff 2482 Jul 13 10:53 ..
Original comment by ger...@gmail.com
on 13 Jul 2012 at 6:09
What about the /usr/local/go/bin directory?
Original comment by a...@google.com
on 13 Jul 2012 at 6:11
yes, there is something there...
$ ls -al /usr/local/Cellar/go/1.0.2/bin/gotour
-rwxr-xr-x 1 gerad staff 5358856 Jul 13 06:30
/usr/local/Cellar/go/1.0.2/bin/gotour
running it seems to work
Original comment by ger...@gmail.com
on 13 Jul 2012 at 9:47
Thanks very much for your help debugging. I'm embarrassed by the user error.
It might make sense to have some output somewhere explaining what is going on
with `go get`. As an example, `npm install` outputs what files and directories
are being created.
Also, I installed go via `brew install go` so this might be an issue with the
homebrew install script, but it looks pretty vanilla:
https://github.com/mxcl/homebrew/blob/475cf029382e3236af362a23dfd5c76d18cc31a0/L
ibrary/Formula/go.rb
Finally, before any of this happened, I was expecting things to be installed
relative to my current directory, and was surprised to see the `GOPATH` stuff
mentioned in other issues. If that bit's always necessary shouldn't it be in
the one-liner install instructions?
Anyway, I'm excited to actually get to play with go now. Thanks again for your
help.
Original comment by ger...@gmail.com
on 13 Jul 2012 at 9:59
another user came on irc today saying 'go get doesn't do anything'. turns out
they followed the install instructions on slide 2 and downloaded a binary
install. the next step is 'go get', but that assumes mercurial, which the user
didn't have.
possible solutions: change the install link to point to
http://golang.org/doc/install/source or provide a tarball/zip archive of the go
tour and document that.
cheers!
Original comment by mirtchov...@gmail.com
on 12 Sep 2012 at 5:06
I just wanted to point out there there are still issues with doing a 'go get
code.google.com/p/go-tour/gotour'. I tried following the instructions on
http://tour.golang.org/#3. At first, it came back with not recognizing 'hg' as
a command. Surprising, but not a big deal.
Then once hg was in my path, I tried again with the go get, and got the below.
As you can see, I'm running the AMD 64 bit 1.0.3 build and it's on Windows 7 64
bit. Anyway, I guess I'll stick with the online version for now, but just
thought someone would like to know about this.
D:\Downloads\go1.0.3.windows-amd64\go\src>go get code.google.com/p/go-tour
package bytes: unrecognized import path "bytes"
package encoding/base64: unrecognized import path "encoding/base64"
package fmt: unrecognized import path "fmt"
package image: unrecognized import path "image"
package image/png: unrecognized import path "image/png"
package runtime: unrecognized import path "runtime"
package math/rand: unrecognized import path "math/rand"
package encoding/json: unrecognized import path "encoding/json"
package flag: unrecognized import path "flag"
package go/ast: unrecognized import path "go/ast"
package go/build: unrecognized import path "go/build"
package go/parser: unrecognized import path "go/parser"
package go/printer: unrecognized import path "go/printer"
package go/token: unrecognized import path "go/token"
package io/ioutil: unrecognized import path "io/ioutil"
package log: unrecognized import path "log"
package net/http: unrecognized import path "net/http"
package os: unrecognized import path "os"
package os/exec: unrecognized import path "os/exec"
package path/filepath: unrecognized import path "path/filepath"
package regexp: unrecognized import path "regexp"
package strconv: unrecognized import path "strconv"
package strings: unrecognized import path "strings"
package sync: unrecognized import path "sync"
Original comment by VincePl...@gmail.com
on 10 Nov 2012 at 9:43
Vince, you most certainly have GOROOT set incorrectly. It defaults to
/usr/local/go. If you put your Go installation somewhere else, GOROOT should be
set to that path.
Run "go env" to see what the go tool thinks your GOROOT is.
Original comment by a...@golang.org
on 15 Nov 2012 at 4:34
Since this bit me, I'll add what helped me out. For those using Homebrew to
install Go, you'll find that `go env` has GOROOT="/usr/local/Cellar/go/1.0.3".
Given that, I simply ran `brew unlink go && brew link go` and then gotour was
available on my regular PATH
Original comment by m...@bjeanes.com
on 21 Nov 2012 at 10:08
Original comment by a...@golang.org
on 2 Jul 2013 at 6:24
Original issue reported on code.google.com by
ger...@gmail.com
on 13 Jul 2012 at 1:39