From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@labs.coraid.com>
Date: Tue, 29 Jun 2010 14:32:01 -0400
To: 9fans@9fans.net
Message-ID: <19b728d48aa74d67b8402c1b9727c80e@coraid.com>
In-Reply-To: <AANLkTimwkYmouvhsYP_EOBc3mAiYY-AgoSIwTeR4HCY1@mail.gmail.com>
References: <AANLkTilfcpui4mNOwlus4PfmN-P1Z5NK4ZGRwE98OFCp@mail.gmail.com>
	<464534aea8c7fffa248a1368c41acb55@proxima.alt.za>
	<AANLkTimXX2a313eMOlHAdzYfCpfr8YYE9-YhEgZPUKOo@mail.gmail.com>
	<AANLkTilKt-m5lRSWKPXiPhH-LxDhMJvBAPWkCBDfbDl0@mail.gmail.com>
	<AANLkTimwkYmouvhsYP_EOBc3mAiYY-AgoSIwTeR4HCY1@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] Go/Inferno toolchain (Was: comment and newline in
Topicbox-Message-UUID: 397bcf2e-ead6-11e9-9d60-3106f5b1d025

> 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