From: andrey mirtchovski <mirtchovski@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Building Go on Plan 9
Date: Fri, 2 Dec 2011 15:12:25 -0700 [thread overview]
Message-ID: <CAK4xykW0ok7ikMi_OwmFZ0bpSSgBXpjs4qXqahsOqh4qNSU5gg@mail.gmail.com> (raw)
In-Reply-To: <867781d7baf5c4e270499faf93e19225@coraid.com>
> if the rule is literally "zero change", then we should give up now.
Russ has been most accommodating with changes in the Go tree. As far
as go portability to Plan 9 is concerned, that's not a problem (except
the few actual problems that need fixing, but that's just code). The
issue is polluting the go tree with yet another build framework which
is 1) not really necessary, 2) about to be taken out anyway and 3)
possible to devise programatically. Russ has said privately (jokingly)
that he'd accept mkfiles if each one said "|<$GOROOT/mkmk.rc Makefile"
and, knowing what we know now, it's not impossible to do.
rminnich-9go's mkfiles for the go package library were mostly created
with such a script.
more important issues exist than just how to build go (which boils
down to "pick any of the 3 current methods and go for it") -- for
example, in order to complete running the full test suite one needs to
solve a signal handling bug in the plan9-specific code of the go
runtime.
next prev parent reply other threads:[~2011-12-02 22:12 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-01 17:48 Anthony Martin
2011-12-01 17:51 ` erik quanstrom
2011-12-01 18:00 ` John Floren
2011-12-01 18:05 ` Stanley Lieber
2011-12-01 18:14 ` Anthony Martin
2011-12-01 18:19 ` Charles Forsyth
2011-12-01 18:25 ` Lyndon Nerenberg
2011-12-01 19:07 ` Anthony Martin
2011-12-01 19:54 ` Lyndon Nerenberg
2011-12-02 3:39 ` Lucio De Re
2011-12-02 14:33 ` Anthony Martin
2011-12-02 14:57 ` erik quanstrom
2011-12-02 15:23 ` Anthony Martin
2011-12-02 17:14 ` Skip Tavakkolian
2011-12-02 15:19 ` Lyndon Nerenberg
2011-12-02 15:59 ` Lucio De Re
2011-12-02 16:09 ` Lucio De Re
2011-12-02 17:24 ` ron minnich
2011-12-02 17:55 ` Lyndon Nerenberg
2011-12-02 17:58 ` Francisco J Ballesteros
2011-12-02 18:19 ` ron minnich
[not found] ` <CAP6exYKKqsc0Kwyhxp_LiXf0oRUJ79UYWZM=Ugp2WPZ7TZATwQ@mail.gmail.c>
2011-12-02 21:42 ` erik quanstrom
2011-12-02 22:12 ` andrey mirtchovski [this message]
2011-12-02 22:13 ` andrey mirtchovski
2011-12-02 17:58 ` Lyndon Nerenberg
2011-12-02 18:01 ` erik quanstrom
2011-12-02 6:34 ` ron minnich
2011-12-02 6:42 ` Lucio De Re
2011-12-02 8:49 ` Francisco J Ballesteros
2011-12-02 17:21 ` ron minnich
2011-12-01 18:28 ` Anthony Martin
2011-12-01 18:30 ` erik quanstrom
2011-12-01 18:45 ` Anthony Martin
2011-12-01 18:48 ` Anthony Martin
2011-12-01 18:18 ` Anthony Martin
2011-12-02 14:40 ` Pavel Zholkover
2011-12-02 14:57 ` Anthony Martin
2011-12-02 20:25 ` [9fans] go v. mk Lyndon Nerenberg
2011-12-02 20:37 ` ron minnich
2011-12-03 0:06 ` Steve Simon
2011-12-03 0:11 ` Lyndon Nerenberg
2011-12-03 0:12 ` ron minnich
2011-12-05 0:32 ` Federico Benavento
2011-12-05 0:44 ` John Floren
2011-12-05 12:20 ` Federico Benavento
2011-12-27 14:38 ` Aram Hăvărneanu
2011-12-01 19:20 [9fans] Building Go on Plan 9 lsub
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=CAK4xykW0ok7ikMi_OwmFZ0bpSSgBXpjs4qXqahsOqh4qNSU5gg@mail.gmail.com \
--to=mirtchovski@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).