From: Matthew Veety <mveety@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] go under plan9 on the radpberry pi?
Date: Thu, 19 Sep 2019 23:26:33 -0400 (EDT) [thread overview]
Message-ID: <alpine.BSF.2.21.99999.352.1909192321240.5516@silverfox.local> (raw)
In-Reply-To: <63A70485-0D01-4D77-9966-3B4CB758F4CC@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 946 bytes --]
Building anything on a raspberry pi is a bit of a chore. I highly
recommend running go on your cpu server and/or local to your filesystem.
The generated binaries seem to work fine. I haven't found any bugs, but I
haven't run anything serious on on my pis.
On Thu, 19 Sep 2019, Michael Misch wrote:
> I’ve used it, it works fine. Building on a raspberry pi, on the other hand is a chore when using Go.
>
>> On Sep 19, 2019, at 3:46 PM, Bakul Shah <bakul@bitblocks.com> wrote:
>>
>> On Thu, 19 Sep 2019 22:41:48 +0100 Steve Simon <steve@quintile.net> wrote:
>>>
>>> does go run under plan9 on the radpberry pi or only on x86?
>>
>> I haven't tried a native build but cross-compiling with
>>
>> cd `go env GOROOT`/src
>> GOOS=plan9 GOARCH=arm ./bootstrap.bash
>>
>> seems to work. bunzip2 the resulting .tbz file in $home & then
>> bind -a $home/go-plan9-arm-bootstrap/bin /bin
>>
>> Only lightly tested.
>>
>
next prev parent reply other threads:[~2019-09-20 3:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 21:41 Steve Simon
2019-09-19 22:46 ` Bakul Shah
2019-09-19 23:15 ` Michael Misch
2019-09-20 3:26 ` Matthew Veety [this message]
2019-09-20 4:37 ` Lyndon Nerenberg
2019-09-20 5:29 ` Steve Simon
2019-09-20 5:32 ` Michael Misch
2019-09-20 6:07 ` Bakul Shah
2019-09-20 8:53 ` Richard Miller
2019-09-21 1:23 ` Bakul Shah
2019-09-21 12:31 ` hiro
2019-09-21 23:55 ` Bakul Shah
2019-09-20 8:43 ` Richard Miller
2019-09-20 17:10 ` Steve Simon
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=alpine.BSF.2.21.99999.352.1909192321240.5516@silverfox.local \
--to=mveety@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).