9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Dave MacFarlane <driusan@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 15:50:29 -0400	[thread overview]
Message-ID: <CAG2UyHqGxE9hU+YRaYuc6ANxu=SS4Oh5WYBLX5sp0QEPixH-Pw@mail.gmail.com> (raw)
In-Reply-To: <C37AE86F-CA3A-40F8-B960-1E244B12AD1E@yahoo.ca>

[-- Attachment #1: Type: text/plain, Size: 1154 bytes --]

I've managed to get Go running on an RPi2 using a similar method, but:

1. You need to make sure you're using go-tip. <= 1.6 doesn't have Plan9/arm
support.
2. I had to apply this patch that Richard Miller sent me to my kernel:

term% diff /n/sources/contrib/miller/9/bcm/mem.h /sys/src/9/bcm/mem.h
55c55
< #define       USTKTOP         0x20000000              /* user segment end
+1 */
---
> #define       USTKTOP         0x40000000              /* user segment end
+1 */

(Then realized that the git client I was writing in Go wasn't ready enough
to use
as a daily driver for developing Go programs under Plan9, so I didn't go
much
further than that and compiling a few test programs..)

-- Dave

On Tue, Apr 12, 2016 at 3:21 PM, Chris McGee <sirnewton_01@yahoo.ca> wrote:

> Hi Skip,
>
> Have you managed to get Go running on an RPi this way?
>
> Cheers,
> Chris
>
> >
> > 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
> >
> >
>
>
>


--
- Dave

[-- Attachment #2: Type: text/html, Size: 2594 bytes --]

  reply	other threads:[~2016-04-12 19:50 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
2016-04-12 19:21   ` Chris McGee
2016-04-12 19:50     ` Dave MacFarlane [this message]
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='CAG2UyHqGxE9hU+YRaYuc6ANxu=SS4Oh5WYBLX5sp0QEPixH-Pw@mail.gmail.com' \
    --to=driusan@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).