From: Skip Tavakkolian <skip.tavakkolian@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Go on Plan 9?
Date: Tue, 12 Apr 2016 12:01:15 -0700 [thread overview]
Message-ID: <CAJSxfm+M7qv7jQj0+Yo04y=3FamxM1S1Fgq2GHChNo=Kj=9z7w@mail.gmail.com> (raw)
In-Reply-To: <EB3EB03B-1F9A-4CF8-ACAB-3061F63B2CDA@yahoo.ca>
[-- Attachment #1: Type: text/plain, Size: 1808 bytes --]
Yes, this works and is the easier of the two methods. Using a desktop OS
and starting no Go compilers:
1. download the Go 1.6 binaries for your desktop OS and install them; set
GOROOT_BOOTSTRAP to that directory (e.g. /usr/local/go)
2. copy the Go 1.6 sources (either the tar.gz or git clone of sources) to
your desktop OS; set GOROOT to that directory (e.g. $HOME/go)
3. build the bootstrap for Plan 9 (i.e. go-plan9-386-bootstrap.tbz) on your
desktop:
$ cd $GOROOT/src
$ GOOS=plan9 GOARCH=386 ./bootstrap.bash
if all is well, this will produce ../../go-plan9-386-bootstrap.tbz
4. untar this in your Plan 9 environment and set GOROOT_BOOTSTRAP to that
directory; e.g. drawterm from your desktop OS to Plan 9:
% cd $home
% bunzip2 -c /mnt/term/path-to-go-plan9-386-bootstrap.tbz | tar -xv
% GOROOT_BOOTSTRAP=$home/go-plan9-386-bootstrap
5. copy Go 1.6 sources to your Plan 9 fs and set GOROOT to that directory;
e.g. drawterm from your desktop OS to Plan 9:
% mkdir $home/go
% dircp /mnt/term/path-of-GOROOT-on-desktop $home/go
% GOROOT=$home/go
% cd $GOROOT/src
% ./all.rc
If you run Plan 9 in a VM, emulator or a confined device (RPi), it will be
easier/faster to cross compile your app and copy it over. E.g. to compile
for 9Pi:
$ GOOS=plan9 GOARCH=arm go build
-Skip
On Mon, Apr 11, 2016 at 5:59 PM, Chris McGee <sirnewton_01@yahoo.ca> wrote:
>
>
> It may also be possible to cross compile a bootstrap of Go from
> Linux/Mac/Windows using the bootstrap.sh script after setting GOOS=plan9,
> GOARCH=386 and GO386=387. That bootstrap can be placed into plan9 and used
> as the GOROOT_BOOTSTRAP to compile a full Go installation on the plan9
> system.
>
>
>
[-- Attachment #2: Type: text/html, Size: 2418 bytes --]
next prev parent reply other threads:[~2016-04-12 19:01 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-12 0:59 Chris McGee
2016-04-12 19:01 ` Skip Tavakkolian [this message]
2016-04-12 19:21 ` Chris McGee
2016-04-12 19:50 ` Dave MacFarlane
2016-04-12 21:26 ` Skip Tavakkolian
2016-04-13 0:18 ` Chris McGee
2016-04-12 21:44 ` sl
2016-04-13 2:50 ` Skip Tavakkolian
2016-04-13 2:59 ` Chris McGee
2016-04-13 7:27 ` lucio
2016-04-13 9:10 ` Richard Miller
2016-04-13 9:10 ` Richard Miller
2016-04-13 13:08 ` Chris McGee
2016-04-13 13:46 ` Richard Miller
2016-04-13 14:00 ` Chris McGee
2016-04-13 14:32 ` Kenny Lasse Hoff Levinsen
2016-04-13 14:32 ` Charles Forsyth
2016-04-13 14:39 ` Richard Miller
2016-04-13 14:42 ` Charles Forsyth
2016-04-13 14:46 ` Richard Miller
2016-04-13 14:46 ` Charles Forsyth
2016-04-13 14:52 ` lucio
2016-04-13 16:12 ` Richard Miller
2016-04-13 7:21 ` lucio
2016-04-13 7:34 ` lucio
2016-04-13 20:38 ` Skip Tavakkolian
-- strict thread matches above, loose matches on Subject: below --
2016-01-26 21:52 sl
2016-01-26 22:03 ` Kenny Lasse Hoff Levinsen
2016-01-26 22:29 ` sl
2016-01-26 22:38 ` David du Colombier
2016-01-27 1:29 ` Matthew Veety
2016-01-26 21:44 Sean Caron
2016-01-26 22:05 ` Skip Tavakkolian
2016-01-26 22:16 ` Sean Caron
2016-01-26 22:32 ` David du Colombier
2016-01-26 22:40 ` David du Colombier
2016-01-27 1:40 ` Sean Caron
2016-01-27 1:52 ` Skip Tavakkolian
2016-01-27 2:24 ` Sean Caron
2016-01-27 4:04 ` lucio
2016-01-27 6:25 ` David du Colombier
2016-01-27 13:45 ` Charles Forsyth
2016-01-26 22:19 ` David du Colombier
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='CAJSxfm+M7qv7jQj0+Yo04y=3FamxM1S1Fgq2GHChNo=Kj=9z7w@mail.gmail.com' \
--to=skip.tavakkolian@gmail.com \
--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).