From: quanstro@labs.coraid.com (erik quanstrom)
Subject: [9fans] all you yacc experts
Date: Fri, 11 Nov 2011 11:09:47 -0500 [thread overview]
Message-ID: <b8b469b07371ed6a4544f98832afcf36@coraid.com> (raw)
In-Reply-To: <CAP6exY+7R9z3uusW683gFCCjvt+t6cZVpq-0TWZL2SiDBbMw3g@mail.gmail.c>
On Fri Nov 11 11:08:13 EST 2011, rminnich at gmail.com wrote:
> Go is pretty solid on 386 and I'm slowly puzzling my way through NIX support.
>
> One thing that stands in the way of full native build is the bison issue.
>
> If somebody wants to look at enhancing yacc so that the extra bison
> bits can be supported, that would probably do the trick. I have no
> idea of the level of effort, I have not looked.
>
> We could run bison under linuxemu; I don't think this approach is as
> good because it still leaves us a bit dependent on some outside force
> for bison binaries. But that might be a good stopgap.
>
> I'm looking forward to Go 1 because I'm pretty sure that most of what
> we've had to do for this version of Go will go away :-)
>
> I'm still amused that the best way to write portable C is to just ship
> a reasonable C compiler with Go and use gcc to build that C compiler,
> and then compile your portable C with it :-)
at one time the go .y wasn't bison dependent. is the new dependency
a choice or requirement?
- erik
next parent reply other threads:[~2011-11-11 16:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAP6exY+7R9z3uusW683gFCCjvt+t6cZVpq-0TWZL2SiDBbMw3g@mail.gmail.c>
2011-11-11 16:09 ` erik quanstrom [this message]
2011-11-11 17:27 ` Lucio De Re
2011-11-11 17:25 ` ron minnich
2011-11-11 18:00 ` Lucio De Re
[not found] <CABT0RTRAXEL454dP+gpC7gYtV9hT7mk+1znEVU0NP4CuKcW=vg@mail.gmail.com>
2011-11-13 22:30 ` Scato Logic
2011-11-13 23:22 ` Bruce Ellis
2011-11-11 16:07 ron minnich
2011-11-11 17:16 ` Steve Simon
2011-11-11 20:54 ` Bakul Shah
2011-11-11 20:58 ` ron minnich
2011-11-11 21:30 ` Bakul Shah
2011-11-11 23:18 ` Steve Simon
2011-11-12 4:51 ` Lucio De Re
2011-11-12 5:15 ` Bruce Ellis
2011-11-12 5:36 ` Lucio De Re
2011-11-12 4:49 ` Lucio De Re
2011-11-11 23:38 ` Iruatã Souza
2011-11-12 9:23 ` Bakul Shah
2011-11-13 0:53 ` Bruce Ellis
2011-11-13 4:48 ` Lucio De Re
2011-11-13 5:55 ` Bruce Ellis
2011-11-13 10:08 ` Steve Simon
2011-11-13 10:30 ` Bruce Ellis
2011-11-13 17:08 ` ron minnich
2011-11-15 21:10 ` Anthony Martin
2011-11-15 21:49 ` David Leimbach
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=b8b469b07371ed6a4544f98832afcf36@coraid.com \
--to=quanstro@labs.coraid.com \
/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).