From: Paul Nasrat <pauln@truemesh.com>
To: linux-8086@vger.kernel.org
Subject: Re: Booting with Elks
Date: Wed, 11 Feb 2004 11:43:01 +0000 [thread overview]
Message-ID: <20040211114300.GM19143@lichen.truemesh.com> (raw)
In-Reply-To: <EDECLJGBBDNMPACDPHMCKEHOCBAA.premke@ess-wowi.de>
On Wed, Feb 11, 2004 at 12:40:15PM +0100, Mario Premke wrote:
> Haven'd had time yet to look at the latest version. Is the compiler now
> running on ELKS itself or is there still the bcc cross compiler?
ELKS is currently not self-hosting, you still need to use bcc to build
If you are feeling particularly adventurous you can also play with the turbo C
stuff for user space, although bcc is currently the prefered, recommended
compiler:
http://www.retepnet.it/alfmar/fhlvnr.html
Paul
next prev parent reply other threads:[~2004-02-11 11:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-10 18:12 Booting with Elks Florian Zimmermann
2004-02-11 10:58 ` David Given
2004-02-11 11:40 ` AW: " Mario Premke
2004-02-11 11:43 ` Paul Nasrat [this message]
[not found] ` <4029B42F.4AED@siol.net>
[not found] ` <1076443760.4034.28.camel@mindfsck>
2004-02-11 19:02 ` Florian Zimmermann
-- strict thread matches above, loose matches on Subject: below --
2004-02-11 12:44 Pat Gilliland
2004-02-11 18:52 ` Florian Zimmermann
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=20040211114300.GM19143@lichen.truemesh.com \
--to=pauln@truemesh.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