public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Grant Edwards <grante@visi.com>
To: "Neundorf, Alexander" <Alexander.Neundorf@jenoptik.com>
Cc: Gregg C Levine <hansolofalcon@worldnet.att.net>,
	eCos Discuss <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Re: eCos on 80186?
Date: Thu, 24 Jun 2004 14:26:00 -0000	[thread overview]
Message-ID: <20040624142650.GA15331@grante.dsl.visi.com> (raw)
In-Reply-To: <5A8A17126B73AC4C83968F6C4505E3C5C7FB07@JO-EX01.JENOPTIK.NET>

On Thu, Jun 24, 2004 at 02:12:17PM +0200, Neundorf, Alexander wrote:

>> What about using the tools for 16 bit arches from DJ Delorie?
>> Oh he claims they are basically unsupported, I don't know if
>> they won't work.
> 
> Maybe you could check out which compiler is used by the ELKS
> project: http://elks.sourceforge.net/ This is intended to run
> a linux-like kernel on 80x86 with x<3

ELKS uses the bcc compiler and ld86 linker from the dev86
package.  Googling for "dev86 bcc" should provide more info.

-- 
Grant Edwards
grante@visi.com

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2004-06-24 14:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-24 12:12 AW: " Neundorf, Alexander
2004-06-24 14:26 ` Grant Edwards [this message]
2004-06-25  5:19   ` Mark Grosberg
  -- strict thread matches above, loose matches on Subject: below --
2004-06-23 15:24 [ECOS] " osrookie
2004-06-23 15:35 ` [ECOS] " Grant Edwards
2004-06-23 20:19   ` John Newlin
2004-06-24  2:35 ` [ECOS] " Paul D. DeRocco
2004-06-24  3:45   ` [ECOS] " Grant Edwards
2004-06-24  6:12     ` Chris Gray
2004-06-24 11:40       ` Gregg C Levine
2004-06-24 14:01       ` Grant Edwards

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=20040624142650.GA15331@grante.dsl.visi.com \
    --to=grante@visi.com \
    --cc=Alexander.Neundorf@jenoptik.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=hansolofalcon@worldnet.att.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 read-only IMAP folder(s) and NNTP newsgroup(s).