9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Skip Tavakkolian <skip.tavakkolian@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Go (again) on plan9/arm
Date: Wed, 10 Apr 2013 15:56:45 -0700	[thread overview]
Message-ID: <CAJSxfmJNrpYeA9WxtOAgeWm9V_YJrBrXJ=M3JKkje1Rj219CPQ@mail.gmail.com> (raw)
In-Reply-To: <20130410202019.6A6EFB82A@mail.bitblocks.com>

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

the process is probably a lot easier with the right cpu type. i think it is
something like:

for each architecture (arm, 386), cpu into a machine with that architecture
and:

for (i in arm 386) {
  GOARCH=$i GOBIN=/$cputype/bin ./all.rc
}

for Sheeva/Guru targets, a GOARM=5 is also needed for arm targets.

still, not as bad as what is required for other OS:
http://dave.cheney.net/2012/09/08/an-introduction-to-cross-compilation-with-go




On Wed, Apr 10, 2013 at 1:20 PM, Bakul Shah <bakul@bitblocks.com> wrote:

> > In the meantime, I'd like some 9fans who may own a Sheevaplug,
> > possibly also other ARM equipment supported by Plan 9 - 9fans with
> > some interest in Go - to try to install Go on their devices.
>
> Can't go be cross-built? Having multiple cross compilers work
> right is one of the best things about plan9's userland.
>
>

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

  reply	other threads:[~2013-04-10 22:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-10 19:21 lucio
2013-04-10 19:53 ` erik quanstrom
2013-04-11  5:48   ` lucio
2013-04-10 20:20 ` Bakul Shah
2013-04-10 22:56   ` Skip Tavakkolian [this message]
2013-04-11  5:40   ` lucio
2013-04-10 21:31 ` Skip Tavakkolian
2013-04-10 23:53 ` Christopher Nielsen

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='CAJSxfmJNrpYeA9WxtOAgeWm9V_YJrBrXJ=M3JKkje1Rj219CPQ@mail.gmail.com' \
    --to=skip.tavakkolian@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).