From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Go on Plan 9?
Date: Wed, 13 Apr 2016 10:10:15 +0100 [thread overview]
Message-ID: <69a9850fdb5870df2b5be63be82f2130@hamnavoe.com> (raw)
In-Reply-To: <1A8D3234-4A50-4A23-AD20-BFDA49A73AB1@yahoo.ca>
> I tried a bootstrapped version on my RPi but it fails with a "fork/exec ... virtual memory allocation failed” error when I try to compile anything.
Go needs a lot of virtual memory - it won't even pass the installation test suite
if you give it less than a gigabyte. That was the reason for the change to the
definition in /sys/src/9/bcm/mem.h mentioned earlier:
< #define USTKTOP 0x20000000 /* user segment end +1 */
---
> #define USTKTOP 0x40000000 /* user segment end +1 */
Are you running a 9pi kernel built with this change? There are newer kernel binaries
in /n/sources/contrib/miller/9pi* with this and other tweaks applied. If you are
using an older pi with 512MB of ram, you'll need to activate swap(8).
The plan9_arm version of go is expected to be in the 1.7 release. It is already
self hosting: if you look at the builder dashboard in http://build.golang.org
which tracks updates being built and tested on all platforms, the "plan9 arm"
column at the far right is a Raspberry Pi 3 managed by David du Colombier.
It doesn't keep up with every update because a complete build and test suite
run takes a bit over an hour.
next prev parent reply other threads:[~2016-04-13 9:10 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
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 [this message]
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=69a9850fdb5870df2b5be63be82f2130@hamnavoe.com \
--to=9fans@hamnavoe.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).