9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lucio De Re <lucio@proxima.alt.za>
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: Wed, 30 Jun 2010 10:17:26 +0200	[thread overview]
Message-ID: <20100630081726.GA19323@mutter.proxima.alt.za> (raw)
In-Reply-To: <AANLkTinKtxq7nnwS86g8ejpECFM8zquorijKcs2NTxyj@mail.gmail.com>

On Tue, Jun 29, 2010 at 04:00:09PM -0700, Russ Cox wrote:
>
> i think people get too hung up on trying to make
> the port back perfect.  just make it work.
> then make it better.
>
But it's the toolchain I'm after.  I like Go a lot, but I feel that
a viable toolchain that produces ELF files for Linux is also a
worthy objective.

And getting the toolchain to produce Plan 9 executable code has
already been done, albeit unchecked and about to be lost or forgotten
on a server a long way from here.

Still, I'd be thrilled to be able to cut my teeth on Go on Plan 9
rather than UBUNTU, so don't let me discourage anyone.  I just want
9fans to know that I'm willing to do the slog work to keep the
toolchains in sync and they shouldn't go out of their way to make
my life unnecessarily difficult :-)

++L



  reply	other threads:[~2010-06-30  8:17 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
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 [this message]
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=20100630081726.GA19323@mutter.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).