From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: Re: [9fans] Go (again) on plan9/arm
Date: Thu, 11 Apr 2013 07:40:00 +0200 [thread overview]
Message-ID: <1f9928315086a72880d03b7a1d748e9c@proxima.alt.za> (raw)
In-Reply-To: <20130410202019.6A6EFB82A@mail.bitblocks.com>
> Can't go be cross-built? Having multiple cross compilers work
> right is one of the best things about plan9's userland.
Yes, it is possible - to answer your question - although I've found
that having Plan 9 as a special, simpler case is actually a (minor)
liability.
I'm not sure how your question relates to the portion of my message
you quoted, my intention here is two-fold: to locate bugs in the build
procedure and testing on the one hand and to help me identify the
essential changes to the Plan 9 distribution that the Go build needs.
The latter is perhaps interference on my part, but the lack of a code
review facility for Plan 9 means that an outsider has no mechanism to
track a parallel development like the Plan 9 distribution. It also
means that no one can be sure (with all the different forks of the
Plan 9 base) what is needed for Go to build on a given one.
It's not my job either to attempt to dictate to Plan 9 developers
anywhere what they need to have in their distributions, nor to grant
Bell Labs higher authority than any of the subsequent forks as the
discriminator. But given that, in my opinion, Go is for Plan 9 is
likely to reach an insurmountable obstacle, this is how I have
approached the problem. Other suggestions are welcome.
++L
next prev parent reply other threads:[~2013-04-11 5:40 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
2013-04-11 5:40 ` lucio [this message]
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=1f9928315086a72880d03b7a1d748e9c@proxima.alt.za \
--to=lucio@proxima.alt.za \
--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).