From: Eric Van Hensbergen <ericvh@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Go/Inferno toolchain (Was: comment and newline in
Date: Tue, 29 Jun 2010 15:45:44 -0500 [thread overview]
Message-ID: <AANLkTil-XnA0Rdn3cZJuLAdRPWKcQofJh3HUu6LgzIhB@mail.gmail.com> (raw)
In-Reply-To: <19b728d48aa74d67b8402c1b9727c80e@coraid.com>
erik's attempt is now in the go-plan9 repo under its own branch for
those that wish to take a look.
Hopefully I merged it properly.
-eric
On Tue, Jun 29, 2010 at 1:32 PM, erik quanstrom
<quanstro@labs.coraid.com> wrote:
>> a) Simple logistics (makefile/script transformations, Sape's branch
>> has some of this, what the right way to do this in order to be
>> integrated back into the mainline go tree is an open question)
> [...]
>>
>> I wonder if one way of avoiding (a) is just to rig to cross-compile
>> from Linux/MacOSX to Plan 9 and get (b) and (c) done first then work
>> back to (a), just because it seems like it would be more satisfying.
>
> i found that (a) wasn't hard. i got everything compiled
> rather quickly, but something came up before i could get
> going on the runtime.
>
> - erik
>
>
next prev parent reply other threads:[~2010-06-29 20:45 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-25 15:35 [9fans] comment and newline in define lucio
[not found] ` <AANLkTilhVWAu8htoIL903rtMK1z9Sw88pSfEASawc5Xi@mail.gmail.com>
2010-06-26 0:50 ` Christopher Nielsen
2010-06-26 0:58 ` erik quanstrom
2010-06-26 4:18 ` Rob Pike
2010-06-26 6:15 ` Christopher Nielsen
2010-06-26 5:19 ` [9fans] Go/Inferno toolchain (Was: comment and newline in define) lucio
2010-06-26 6:46 ` Christopher Nielsen
2010-06-26 9:26 ` [9fans] Go/Inferno toolchain (Was: comment and newline in lucio
2010-06-26 10:34 ` erik quanstrom
2010-06-26 11:00 ` lucio
2010-06-28 22:03 ` Eric Van Hensbergen
2010-06-29 17:24 ` Rob Pike
2010-06-29 17:31 ` Devon H. O'Dell
2010-06-29 17:36 ` Francisco J Ballesteros
2010-06-29 17:48 ` Francisco J Ballesteros
2010-06-29 18:02 ` Jack Johnson
2010-06-29 18:10 ` Eric Van Hensbergen
2010-06-29 18:12 ` Francisco J Ballesteros
2010-06-29 20:30 ` Eric Van Hensbergen
2010-06-29 18:32 ` erik quanstrom
2010-06-29 20:45 ` Eric Van Hensbergen [this message]
2010-06-29 20:52 ` erik quanstrom
2010-06-29 21:03 ` ron minnich
2010-06-29 21:36 ` Steve Simon
2010-06-29 21:54 ` Charles Forsyth
2010-06-30 9:25 ` Lucio De Re
2010-06-29 22:35 ` cinap_lenrek
2010-06-29 23:00 ` Russ Cox
2010-06-30 8:17 ` Lucio De Re
2010-06-29 21:15 ` Devon H. O'Dell
2010-06-29 21:27 ` ron minnich
2010-06-26 7:37 ` [9fans] Go/Inferno toolchain (Was: comment and newline in define) Ethan Grammatikidis
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=AANLkTil-XnA0Rdn3cZJuLAdRPWKcQofJh3HUu6LgzIhB@mail.gmail.com \
--to=ericvh@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).