> GOROOT=/sys/src/golang #where the go repository resides
> GOOS=plan9
> GOARCH=$objtype
> GOHOSTARCH=$cputype
> GOBIN=/$objtype/bin
> GOPATH=/sys/src/go #wher your go stuff resides
> GOARM=5 #or 6 or 7, depending on your machine's support of floating point.
> GOEXPERIM=''
Of the above, I think GOROOT is computed as ".." during build (from
$GOROOT/src), GOOS and GOARCH can be used to override the defaults,
which are as given by Gorka, to the best of my knowledge. GOHOSTOS
and GOHOSTARCH are almost certainly fine as computed, CGO_ENABLED is
useful and fussy: I would definitely recommend setting it to "0" for
Plan 9 use, it bites me every time I leave it unassigned.
GOBIN should be <something>/$objtype/bin in my opinion, I use
$home/bin/386 for experimental use.
GOEXPERIMENT is lost in the fog of time in my memory. I haven't used
it or needed it for months.
My "go env" on plan9/386:
term% go env
GOARCH='386'
GOBIN='/usr/lucio/bin/386'
GOCHAR='8'
GOEXE=''
GOHOSTARCH='386'
GOHOSTOS='plan9'
GOOS='plan9'
GOPATH='/home/Project/usr/lucio/Project'
GORACE=''
GOROOT='/n/go'
GOTOOLDIR='/n/go/pkg/tool/plan9_386'
CGO_ENABLED='0'
Note the weird GOPATH, it looks as follows in real life, I must report
this as an issue. I haven't had a chance to prove that it's a
problem.
term% echo $GOPATH
/home/Project /usr/lucio/Project
/home/ (and sometimes /n/home/ - it varies) is where I map
/home/lucio/ from foreign servers; no one needs to do that, it may be
a crazy idea.
And for those who may be curious, this is for the Sheeva:
bangle% go env
GOARCH='arm'
GOBIN='/usr/lucio/bin/arm'
GOCHAR='5'
GOEXE=''
GOHOSTARCH='arm'
GOHOSTOS='plan9'
GOOS='plan9'
GOPATH='/home/Project/usr/lucio/Project'
GORACE=''
GOROOT='/n/go'
GOTOOLDIR='/n/go/pkg/tool/plan9_arm'
CGO_ENABLED='0'
++L
