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
feedback for binary distro freebsd-386 #3212
Labels
Comments
Just tried on FreeBSD 8.2-RELEASE-p3/i386 with following procedure: 1. untar ... ok 2. run go version ... ok 3. run go test -v -short ... ok 4. run go test -v ... two issues detected, filed as issue #3225 and issue #3226. |
FreeBSD codepic.nfshost.com FreeBSD 8.2-RELEASE-p5 #11: Sat Dec 24 01:38:45 UTC 2011 untarred to ~/go, tested go version, go get, go install, executed sample programs from github.com/ajstarks/svgo: webfonts > /home/public/webfonts.svg bubtrail > /home/public/bubtrail.svg svgdef > /home/public/svgdef.svg test by visiting http://codepic.nfshost.com/webfonts.svg http://codepic.nfshost.com/bubtrail.svg http://codepic.nfshost.com/svgdef.svg all working as expected. |
Works on FreeBSD/386 -- the recipe: $ uname -a FreeBSD codepic.nfshost.com 8.2-RELEASE-p5 FreeBSD 8.2-RELEASE-p5 #11: Sat Dec 24 01:38:45 UTC 2011 root@x3:/usr/obj/usr/src/sys/NFSN32 i386 $ env | grep '^GO' GOROOT=/home/private/go GOPATH=/home/private/gocode $ echo $PATH /usr/local/php5/bin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/usr/X11R6/bin:/home/private/go/bin:/home/private/gocode/bin $ wget 'http://go.googlecode.com/files/go.weekly.2012-03-13.freebsd-386.tar.gz' # fet the binary package $ rm -rf go # remove the old go tree $ tar xzvof go.weekly.2012-03-13.freebsd-386.tar.gz # untar $ go version # check the go version weekly.2012-03-13 go install github.com/ajstarks/svgo/... ls -l $GOPATH/bin # show newly build binaries ls -l $GOPATH/pkg/freebsd_386/github.com/ajstarks # show updated library $ flower > /home/public/flower.svg # run a command |
This issue was closed.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The text was updated successfully, but these errors were encountered: