9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: David du Colombier <0intro@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Go on Plan 9?
Date: Tue, 26 Jan 2016 23:19:53 +0100	[thread overview]
Message-ID: <CANUoZoHj5DbFmCuOO9LBP3+5P5-1HwsFnvUC55SsY-JBGJwE3g@mail.gmail.com> (raw)
In-Reply-To: <CAJSxfmJDb9ZmRducTPnB0irjeO7o1dr6HsT7kjSELxN_J=G-Vw@mail.gmail.com>

> All the errors seem related to the old Rune size. I suspect you're running
> an old system and it's likely to not have nsec and tsemacquire syscalls
> either.
>
> If you believe the system is up-to-date, you can cross compile a simple Go
> program using 1.5 or later targeting GOOS=plan9 GOARCH=386 from a Linux/OSX
> or Windows box and see if it runs on your system.  That might give you more
> info.

Yes, Skip is right. On your system Rune is defined as ushort instead of uint.
The change from ushort to uint was done in April 2013.

While you could successfully cross-compile Go 1.5, it will probably
not work on your machine. In fact, the nsec system call will likely be
missing as well, since it was introduced in Plan 9 in May 2014.

You should update your system.

Since plan9.bell-labs.com is currently down, you could either change
your 9fs script and change it to pull from 9p.io, like this:

http://9legacy.org/9legacy/patch/9fs-9p.io.diff

Or use the latest Plan 9 CD image:

http://9p.io/plan9/download/plan9.iso.bz2

Then, you will be able to compile and execute Go 1.4, 1.5 and 1.6 successfully.

--
David du Colombier



  parent reply	other threads:[~2016-01-26 22:19 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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-04-12  0:59 Chris McGee
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

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=CANUoZoHj5DbFmCuOO9LBP3+5P5-1HwsFnvUC55SsY-JBGJwE3g@mail.gmail.com \
    --to=0intro@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).