From: Steve Simon <steve@quintile.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Cc: Lyndon Nerenberg <lyndon@orthanc.ca>
Subject: Re: [9fans] go under plan9 on the radpberry pi?
Date: Fri, 20 Sep 2019 06:29:31 +0100 [thread overview]
Message-ID: <B2EF8F9D-B63C-4F8E-8ACF-3F20436484FD@quintile.net> (raw)
In-Reply-To: <293bcab7a51132f9@orthanc.ca>
hi,
my plan was to build and run/debug go on a raspberry pi 4 running plan9, not to cross compile.
i am confident in the linux cross compile environment i was just concerned about the plan9 os/runtime support for the pi.
i guess it comes down to plan9 os interface for the arm.
people said it is painful, you mean the pi is slow?
thanks for the help.
-Steve
> On 20 Sep 2019, at 5:37 am, Lyndon Nerenberg <lyndon@orthanc.ca> wrote:
>
> Matthew Veety writes:
>
>> Building anything on a raspberry pi is a bit of a chore. I highly=20
>> recommend running go on your cpu server and/or local to your filesystem.=20
>> The generated binaries seem to work fine.
>
> Go does wonderfully when it comes to generating binaries for
> non-native architectures. I have a few Go-based tools I use at
> work that I build on any number of archictures (macos, freebsd,
> openbsd, linux / armX, i386, amd64)) that I need to run on one or
> many of the above. They all just work. Makes debugging a breeze.
>
> But now that they are succumbing to the shared lib/obj doctrine, I'm sure
> I will soon go back to writing C code, since the advantage of those
> static go binaries is about to be lost :-(
next prev parent reply other threads:[~2019-09-20 5:29 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
2019-09-20 4:37 ` Lyndon Nerenberg
2019-09-20 5:29 ` Steve Simon [this message]
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=B2EF8F9D-B63C-4F8E-8ACF-3F20436484FD@quintile.net \
--to=steve@quintile.net \
--cc=9fans@9fans.net \
--cc=lyndon@orthanc.ca \
/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).