9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lyndon Nerenberg <lyndon@orthanc.ca>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] go v. mk
Date: Fri,  2 Dec 2011 12:25:16 -0800	[thread overview]
Message-ID: <alpine.OSX.1.10.1112021219270.91234@peregrin.orthanc.ca> (raw)
In-Reply-To: <20111201174858.GA23075@dinah>

My freebsd-current flamewar is dying out, so time for something new ...

Why are parallel mkfiles in the /go tree considered eeevil?  They seemed
to be very low overhead.  Surely accomodations are being made for Windows.

Regardless, if we want native go, is it that unreasonable to maintain a
port ala spin?  My fiddling with the go tree makes me think it isn't that
hard to set up an overlay that adopts the live go tree to what Plan9 needs
for a build.  bind(1) is a wonderful thing -- we should use it!

The most dynamic part of the go source tree these days seems to be
pkg/Makefile (as far as a native build is concerned).  It can't be that
hard to parse out DIR= from there and turn it into a native mkfile.



  parent reply	other threads:[~2011-12-02 20:25 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-01 17:48 [9fans] Building Go on Plan 9 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
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 ` Lyndon Nerenberg [this message]
2011-12-02 20:37   ` [9fans] go v. mk 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

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=alpine.OSX.1.10.1112021219270.91234@peregrin.orthanc.ca \
    --to=lyndon@orthanc.ca \
    --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).