9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: presotto@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: Cross-platform
Date: Mon,  1 Jan 2001 14:57:40 -0500	[thread overview]
Message-ID: <20010101195741.52B3D199E7@mail.cse.psu.edu> (raw)

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

SOme kind soul may lend you access to a cpu server to work from.

[-- Attachment #2: Type: message/rfc822, Size: 3786 bytes --]

From: "Bryan W. Headley" <bheadley@interaccess.com>
To: rob pike <rob@plan9.bell-labs.com>
Cc: 9fans@cse.psu.edu
Subject: [9fans] Re: Cross-platform
Date: Mon, 01 Jan 2001 12:49:27 -0600
Message-ID: <3A50D137.97FA3030@interaccess.com>

rob pike wrote:

> first, this is the sort of question for comp.os.plan9.
> that aside, gcc doesn't generate plan 9 binaries (yet) and
> the 386 c compiler doesn't run on linux (although it
> wouldn't be very hard to make it do so).
> on the other hand, to port drivers there's no reason
> to do either: copy the source to the appropriate place
> and get to work with the native compiler.
> publish the results and wait for gratitude to rain upon you.

Okay, but I only have the boot floppy to work from to do the final compile.
Probably not enough scratch space for rebuilding the kernel. This ought to be
fun :-)

>
>   ------------------------------------------------------------------------
>
> Subject: Cross-platform
> Date: Sun, 31 Dec 2000 13:05:31 -0600
> From: "Bryan W. Headley" <bheadley@interaccess.com>
> To: rob pike <rob@plan9.bell-labs.com>
> Newsgroups: comp.os.plan9
>
> Rob,
>
> Got a PC with different SCSI and ethernet than what's supported out of
> the box (Initio and pcnet32). It's an old AMD Linux box. Anyway, I have
> the plan9 CD, and could retrofit the Linux drivers to work with p9.
> Question is, is there a cross-platform building strategy? Do I have any
> business expecting gcc to make p9 binaries, or build the '386 C compiler
> to run on Linux?
>
> Just a newbie (it might be written down somewhere, but I haven't found
> it after an hour's search :-)
>
> --
> ____               .:.                 ____
> Bryan W. Headley - bheadley@interaccess.com

--
____               .:.                 ____
Bryan W. Headley - bheadley@interaccess.com



             reply	other threads:[~2001-01-01 19:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-01 19:57 presotto [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-01-01 19:07 Russ Cox
2001-01-01 21:53 ` William K. Josephson
2001-01-01 21:59 ` William K. Josephson
2001-01-02 17:51 ` Randolph Fritz
2001-01-02 21:52   ` William K. Josephson
     [not found] <200101011841.f01IfIf01104@cactus.bheadley.org>
2001-01-01 18:49 ` Bryan W. Headley

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=20010101195741.52B3D199E7@mail.cse.psu.edu \
    --to=presotto@plan9.bell-labs.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).