From: LyricalNanoha@dosius.net (Lyrical Nanoha)
Subject: [TUHS] Redoing "V6on286" or porting V7...?
Date: Wed, 16 Nov 2005 16:41:38 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.62.0511161637001.14020@static-141-149-129-16.buff.east.verizon.net> (raw)
In-Reply-To: <20051114194946.GE6574@gsmx07.alcatel.com.au>
I'm the original poster of this thread.
On Tue, 15 Nov 2005, Peter Jeremy wrote:
> Wesley Parish mentioned bcc and OpenWatcom. I looked into the former
> and it's probably the best starting point (though, with due respect to
> BDE, the code it generates could be better). Assuming that Unix fits
> into the C subset implemented by bcc, you'd be better off spending the
> effort on improving bcc than porting PCC. At the time I looked,
> OpenWatcom was either still vapourware or not self-hosting.
I don't think everything needs to be bootstrapped with an open-source
compiler. I have Turbo C++ 1.01 which is a more than adequate C compiler
for anything I've done with it (ranging from clones of Unix tools to a
COMMAND.COM to an Apple //e emulator). Whatever does the job is fine for
me.
So getting the kernel up and getting files in and out of the image until a
native C compiler is ready (pcc?) can be done with anything, practically.
QEMU is a good enough testbed, and gives you well-defined hardware. Once
everything is up and running, then maybe one can migrate on to newer
systems (V7, 2BSD), though V6 should be simple enough as a starting point,
provided most of it is in C (I haven't really looked).
-uso.
next prev parent reply other threads:[~2005-11-16 21:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-09 17:26 Lyrical Nanoha
2005-11-09 21:54 ` M. Warner Losh
2005-11-09 22:03 ` Brantley Coile
2005-11-12 6:13 ` Albert Cahalan
2005-11-12 13:18 ` Brantley Coile
2005-11-13 20:16 ` Peter Jeremy
2005-11-14 9:38 ` Wesley Parish
2005-11-14 15:45 ` Brantley Coile
[not found] ` <8a61b612cf43394f33e6531339fe4263@coraid.com>
2005-11-14 19:49 ` Peter Jeremy
2005-11-14 20:31 ` Brantley Coile
2005-11-16 21:41 ` Lyrical Nanoha [this message]
[not found] ` <17277.62390.986234.433543@hod.localdomain>
2005-11-18 17:59 ` Lyrical Nanoha
2005-11-19 4:17 ` Brantley Coile
2005-11-15 3:08 ` Greg Haerr
2005-11-15 3:40 ` Peter Jeremy
2005-11-15 13:30 ` Brantley Coile
2005-11-14 21:34 Norman Wilson
2005-11-14 22:59 ` Brantley Coile
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=Pine.LNX.4.62.0511161637001.14020@static-141-149-129-16.buff.east.verizon.net \
--to=lyricalnanoha@dosius.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).