9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Marshall Conover <marzhall.o@gmail.com>
To: "9fans@9fans.net" <9fans@9fans.net>
Subject: Re: [9fans] Making available a pre-compiled go binary for Miller's plan-9 Pi image (Chris McGee)
Date: Fri, 28 Oct 2016 19:31:16 +0000	[thread overview]
Message-ID: <CAK0pxsEWQT0g43nvHhJZTdigFDLuMH38YW-w4VAwrRQBk0UfRw@mail.gmail.com> (raw)

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

> An alternative to building a Go 1.4.3 bootstrap environment, is to build a
Go 1.7 bootstrap environment for Plan 9 in a mainstream environment ...

> If you want to build the current Go source from scratch on plan9/386,
you can just do...

The binary I built was specifically for arm (or more accurately, for the
raspi), on which I initially spent a chunk of time trying to get 1.4
building; eventually, as suggested here, cross-compiling on my Linux box
was how I ended up getting things working. However, that process wasn't
really intuitive, and felt a good chunk like wasted time.

I figured having a binary available would save people some hassle; there's
no real reason to make everyone cross-compile the binary, especially with
as small a target platform as the pi, and for people like myself who
weren't immediately aware of exactly what to do, it's more things to figure
out for no real reason. Bandwidth is cheap, the binary's small, so I
figured having it around would help other people who install plan 9 on
their Pi to check it out.

I'm already hosting it myself, but it seems like my link got me
spam-filtered. I'm more just wondering where to make it more obvious that
it's available, so noobies like myself can just grab it and play instead of
having to spin the same wheels I did.

Thanks!

mars

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

             reply	other threads:[~2016-10-28 19:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-28 19:31 Marshall Conover [this message]
2016-10-28 20:14 ` David du Colombier
2016-10-29 12:49   ` Chris McGee
2016-10-29 18:46     ` David du Colombier
2016-10-30  2:13       ` Chris McGee
2016-10-30  8:39         ` David du Colombier
2016-10-31  1:08           ` Chris McGee
2016-10-31  1:47             ` Stanley Lieber
2016-11-01 13:05               ` Chris McGee
2016-11-13 18:07                 ` David du Colombier
2016-11-13 18:26                   ` Chris McGee
2016-11-13 18:49                     ` 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=CAK0pxsEWQT0g43nvHhJZTdigFDLuMH38YW-w4VAwrRQBk0UfRw@mail.gmail.com \
    --to=marzhall.o@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).