From: "tom potts" <madtom1999@yahoo.com>
To: linux-8086@vger.kernel.org
Subject: Developer Resources!!
Date: Wed, 4 Sep 2002 08:42:25 +0100 (BST) [thread overview]
Message-ID: <20020904074225.44727.qmail@web13302.mail.yahoo.com> (raw)
In-Reply-To: <20020904073015Z319091-685+42553@vger.kernel.org>
Hi,
I've been out of the loop for a while so I may be
repeating an earlier mailing but potentially great
news:
Open Watcom (http://www.openwatcom.org/) has released
the source code for the original 16 bit C compiler and
tools!!
It should be possible to modify this to actually run
under ELKS so one should be able to do ones
development in situ and bring ELKS to 'stand alone
level'.
I've got my first child due soon but if anyones
intereseted in getting together and porting this over
I'd be glad to get involved.
Tom
__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com
next parent reply other threads:[~2002-09-04 7:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020904073015Z319091-685+42553@vger.kernel.org>
2002-09-04 7:42 ` tom potts [this message]
2002-09-23 19:27 Developer Resources!! Ivan Popov
2002-09-24 7:49 ` tom potts
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=20020904074225.44727.qmail@web13302.mail.yahoo.com \
--to=madtom1999@yahoo.com \
--cc=linux-8086@vger.kernel.org \
/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