9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] Go Plan9 ARM Dreamplug
Date: Mon, 15 Apr 2013 12:37:09 +0200	[thread overview]
Message-ID: <bb24c04a9001a3feefb3264e3c73af4b@proxima.alt.za> (raw)
In-Reply-To: <CACm3i_j2=OactingsNSfw14qsxYEqx_iQvHBtQ5tRdKcdj-yeA@mail.gmail.com>

> 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




      parent reply	other threads:[~2013-04-15 10:37 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-15  7:00 Christopher Nielsen
2013-04-15  7:04 ` andrey mirtchovski
2013-04-15  8:10   ` Christopher Nielsen
2013-04-17  9:15     ` Yaroslav
2013-04-17 16:36       ` [9fans] Arm Python Was: " Matthew Veety
2013-04-17 16:40         ` Charles Forsyth
2013-04-17 16:42         ` erik quanstrom
2013-04-15  7:08 ` [9fans] " Gorka Guardiola
2013-04-15  8:12   ` Christopher Nielsen
2013-04-15  8:22     ` Skip Tavakkolian
2013-04-15  8:31       ` kernel panic
2013-04-15  8:43         ` Gorka Guardiola
2013-04-15  9:02           ` kernel panic
2013-04-15  9:55             ` lucio
2013-04-15 11:02               ` Charles Forsyth
2013-04-15 11:21                 ` lucio
2013-04-15  8:33       ` Christopher Nielsen
2013-04-15  8:34       ` Gorka Guardiola
2013-04-15  9:02         ` Skip Tavakkolian
2013-04-15 10:37         ` lucio [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bb24c04a9001a3feefb3264e3c73af4b@proxima.alt.za \
    --to=lucio@proxima.alt.za \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).