9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: David Leimbach <leimy2k@gmail.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 09:00:54 -0800	[thread overview]
Message-ID: <3e1162e60601180900o66ead1b4r81b5a30f67dde478@mail.gmail.com> (raw)
In-Reply-To: <43CE6295.6090908@lanl.gov>

[-- Attachment #1: Type: text/plain, Size: 2195 bytes --]

On 1/18/06, Ronald G Minnich <rminnich@lanl.gov> wrote:
>
> alexandr babic wrote:
> > i think 9fans should write plan9 native programs not trying other waste
> > to import.
>
> right, but I was not trying to do that.
>
> I'm trying to see
> - if I can get L4KA to build (fails)



Never had a problem here... I even cross compile from Mac OS X.  Just gotta
use the right version of the compiler.  [Stupid, I agree, and circle gets
the square]

See this for some potential hints... Of course it's PPC specific but it may
help you figure out why stuff won't build in general.

http://l4ka.org/projects/pistachio/powerpc/ppc-build.txt

Been a while since I've tried this myself but I was very successful back
then [1.5 years ago?]

- get L4KA to boot linux (predicated on previous step)


I think I only ever ran a Live CD of this... but it worked great with the
Dresden Realtime OPerating Systems demo floppy or CD or whatever it was...
They have a really weird windowing system for launching Debian on L4
instances.... this was quite a bit before Xen mind you and they were doing
the same things but on a microkernel that had less suck than mach.

- run Plan 9 as an L4KA guest (predicated on previous step)


I'd try that :)  The weird thing is you can load l4-linux and then write an
OS personality in another address space and use the L4 messaging to use
linux as something of a driver repository.  There are even some performance
measurments of the impact of this, which is a ton better than trying to
write drivers in userspace with mach.  I wouldn't try 10Gbit ethernet that
way but for disks and some other devices this seems to work kind of well.

Abstract here:
http://os.inf.tu-dresden.de/EZAG/old/ws2004/abstracts/abstract_20041012.xml

Sometimes I wish I could just get paid to play with esoteric weird OS junk
all day.

  so far, failure all around.
>
> "he who lives by the gcc hack, dies by the gcc hack" (even on linux)



yep, I'm at least glad that I see more and more -std=c99 in the FreeBSD
build system.  Less and less gcc-isms is a big plus, even if I don't care
for C99 so much [which could be worse].


ron
>

[-- Attachment #2: Type: text/html, Size: 3350 bytes --]

  parent reply	other threads:[~2006-01-18 17:00 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
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 [this message]
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=3e1162e60601180900o66ead1b4r81b5a30f67dde478@mail.gmail.com \
    --to=leimy2k@gmail.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).