From: David Given <dg@cowlark.com>
To: linux-8086@vger.kernel.org
Subject: Re: using elks-libc for DOS development
Date: Fri, 5 Mar 2004 11:03:18 +0000 [thread overview]
Message-ID: <200403051103.19224.dg@cowlark.com> (raw)
In-Reply-To: <20040305074216.GE3291@dbz.icequake.net>
On Friday 05 March 2004 7:42 am, Ryan Underwood wrote:
[...]
> Besides ELKS libc, are there any other free C libraries suitable for
> 16-bit DOS application development? I find a 16-bit version of DJGPP,
> but it has no C library. :( I would use a 32-bit version of DJGPP, but
> the device only has 512k of memory; the necessity of the DPMI server
> would be a waste, as well as the bloat of glibc. I guess there is
> Open Watcom now, but does anyone have experience doing small footprint
> (8086 <= 1MB) C development with it?
Nope. I gather it works, though.
However, if you know where to look there are a number of free 16-bit DOS
compilers. Leaving aside all the various CP/M86 compilers --- which tend to
be K&R only and only compile tiny mode --- a quick web search reveals these:
http://www.htsoft.com/products/pacific/
http://www.digitalmars.com/download/freecompiler.html
You may be better off sticking with Turbo C, however; it is free, and you seem
to be set up for it.
--
+- David Given --McQ-+ Q: What's yellow and equivalent to the axiom of
| dg@cowlark.com | choice?
| (dg@tao-group.com) | A: Zorn's Lemon.
+- www.cowlark.com --+
next prev parent reply other threads:[~2004-03-05 11:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-05 7:42 using elks-libc for DOS development Ryan Underwood
2004-03-05 11:03 ` David Given [this message]
2004-03-05 21:44 ` Ryan Underwood
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=200403051103.19224.dg@cowlark.com \
--to=dg@cowlark.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