From: Eirik Johnson <falmarian@yahoo.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] GNU binutils: you can't make this shit up
Date: Wed, 18 Jan 2006 04:55:42 -0800 [thread overview]
Message-ID: <20060118125542.74124.qmail@web32702.mail.mud.yahoo.com> (raw)
In-Reply-To: <3e1162e60601151947x115c4059rd8b2b857a0129cee@mail.gmail.com>
It does seem odd to use the GNU extensions there,
especially as L4Ka people can't be too cozy with FSF
people, the whole L4Ka::Pistachio is released under
the BSD license.
Quinn
--- David Leimbach <leimy2k@gmail.com> wrote:
> On 1/15/06, erik quanstrom <quanstro@quanstro.net>
> wrote:
> > l4 depends on all that gnu stuff?
> >
> > it's hard to imagine something that bills itself
> as the ultimate
> > microkernel depending on the ultimate macro
> environment.
> >
> > - erik
> >
>
> Depends on the implementation... L4 Pistachio
> requires C++ and a
> particular version of gcc. I've built it on my Mac
> OS X environment
> successfully and run piggybacked images since we had
> no multi-boot
> capable loaders for OpenFirmware at the time.
>
> dave
>
> > Ronald G Minnich <rminnich@lanl.gov> writes
> >
> > |
> > | Andy Newman wrote:
> > | > But luckily there's only one array parameter
> > | > so the error is not that much of a challenge.
> > |
> > |
> > | um. you have not waded through the GNU ifdef
> hell, I'm guessing.
> > |
> > | I have an even better one, in which a struct is
> forward declared, and
> > | included, and so on .... and it's still not
> found as a defined struct.
> > |
> > | And, of course, you can't just cd into a
> binutils directory and try to
> > | make something; no sir, because about 30
> environment variables are
> > | missing at that point.
> > |
> > | whew. Sorry, this is trying to see if the L4
> microkernel can run a Plan
> > | 9 guest.
> > |
> > | ron
> >
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
next prev parent reply other threads:[~2006-01-18 12:55 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-16 1:50 Ronald G Minnich
2006-01-16 2:00 ` Andy Newman
2006-01-16 3:10 ` Ronald G Minnich
2006-01-16 3:19 ` erik quanstrom
2006-01-16 3:47 ` David Leimbach
2006-01-18 12:55 ` Eirik Johnson [this message]
2006-01-18 13:45 ` Bruce Ellis
2006-01-18 14:00 ` alexandr babic
2006-01-18 15:45 ` Ronald G Minnich
2006-01-18 16:45 ` Bruce Ellis
2006-01-18 17:00 ` alexandr babic
2006-01-18 17:04 ` Bruce Ellis
2006-01-18 17:00 ` David Leimbach
2006-01-18 17:14 ` Ronald G Minnich
2006-01-19 8:29 ` Eirik Johnson
2006-01-19 10:34 ` Charles Forsyth
2006-01-19 10:43 ` Bruce Ellis
2006-01-19 10:46 ` erik quanstrom
2006-01-19 10:52 ` Bruce Ellis
2006-01-19 15:41 ` Ronald G Minnich
2006-01-19 16:05 ` David Leimbach
2006-01-19 16:15 ` [9fans] GNU binutils: you can't make this stuff up Brantley Coile
2006-01-19 17:16 ` Bruce Ellis
2006-01-19 22:24 ` erik quanstrom
2006-01-16 17:43 ` [9fans] GNU binutils: you can't make this shit up Ronald G Minnich
2006-01-16 3:46 ` David Leimbach
2006-01-16 17:44 ` Ronald G Minnich
2006-01-16 19:09 ` Bruce Ellis
2006-01-16 7:48 ` Andy Newman
2006-01-16 9:08 ` Bruce Ellis
2006-01-16 12:06 ` erik quanstrom
2006-01-16 13:23 ` Bruce Ellis
2006-01-16 19:17 jmk
2006-01-16 19:26 ` Bruce Ellis
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=20060118125542.74124.qmail@web32702.mail.mud.yahoo.com \
--to=falmarian@yahoo.com \
--cc=9fans@cse.psu.edu \
/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).