9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Chris McGee <sirnewton_01@yahoo.ca>
To: 9fans@9fans.net
Subject: Re: [9fans] Go on Plan 9?
Date: Mon, 11 Apr 2016 20:59:45 -0400	[thread overview]
Message-ID: <EB3EB03B-1F9A-4CF8-ACAB-3061F63B2CDA@yahoo.ca> (raw)

Hi All,

A while back there was a thread about getting newer versions of Go running on plan9. In particular there was a panic related to a floating point error.

In case anyone is interested I have managed to get the newest version of Go working on plan9/386 within virtualbox despite having a similar floating point error as was mentioned here before in that thread.

1) Download, extract and compile Go 1.4.3 from the source tarball
New versions of Go require older versions in order to compile through a bootstrapping process.
This is the last version that can be compiled without bootstrapping.
Modify the include/plan9/386/u.h and remove the line that has a typedef for intptr (in my 9front install this is already declared elsewhere).
Run the make.rc script in the src directory (don’t run all of the tests as many of them appear to fail)

2) Download, extract and compile Go 1.5.3
Set GOROOT_BOOTSTRAP to the go directory for 1.4.3 compiled above
Set GO386=387 (this is important as there appears to be a problem with sse2 floating point with Go in my environment - plan9/386/virtualbox)
https://github.com/golang/go/issues/15234
Run the make.rc script (skip the tests for now)

3) Download, extract and compile Go 1.6
Set GOROOT_BOOTSTRAP to the 1.5.3 go directory
Run the all.rc script

Step 2 may not be necessary, but it worked for me this way.

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.

I hope that this is useful information for others who are trying to get Go working on plan9.

Cheers,
Chris


             reply	other threads:[~2016-04-12  0:59 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-12  0:59 Chris McGee [this message]
2016-04-12 19:01 ` Skip Tavakkolian
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=EB3EB03B-1F9A-4CF8-ACAB-3061F63B2CDA@yahoo.ca \
    --to=sirnewton_01@yahoo.ca \
    --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).