Skip to content


Subversion checkout URL

You can clone with
Download ZIP


feedback for binary distro freebsd-386 #3212

adg opened this Issue · 7 comments

4 participants

adg commented
Please describe your experiences with the freebsd-386 binary distribution, both positive
and negative, here. Thanks.

Comment 1:

I am currently unable to test the FreeBSD/386 binary distribution, but I would like to
see it provided in a FreeBSD native package tools format. This will make it easier for
people to install / upgrade in the future.

Comment 2:

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.

Comment 3:

FreeBSD 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

webfonts > /home/public/webfonts.svg
bubtrail > /home/public/bubtrail.svg
svgdef > /home/public/svgdef.svg

test by visiting

all working as expected.

Comment 4:

Works on FreeBSD/386 -- the recipe:

$  uname -a
FreeBSD 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'
$ echo $PATH

$ wget ''  # 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
ls -l $GOPATH/bin  # show newly build binaries
ls -l $GOPATH/pkg/freebsd_386/  # show updated library
$ flower > /home/public/flower.svg  # run a command

Comment 5:

weekly 2012-03-22, 
repeated procedure from comment #4 (now a script), runs fine.

Comment 6:

Labels changed: added priority-later.


Comment 7:

Closing these issues now that Go 1 is out. Please create a new issue for any problem
with the binary distributions.

Status changed to Done.

@adg adg self-assigned this
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.