From: Javier Sedano <javier.sedano@agora-2000.com>
To: Eduardo Pereira Habkost <ehabkost@conectiva.com.br>
Cc: Miguel Bolanos <mike@linuxlabs.com>, linux-8086@vger.kernel.org
Subject: Re: Future of ELKS
Date: Thu, 20 May 2004 19:30:11 +0200 [thread overview]
Message-ID: <40ACEB23.7010101@agora-2000.com> (raw)
In-Reply-To: <20040520153744.GL24490@duckman.distro.conectiva>
Hi,
Eduardo Pereira Habkost wrote:
>
> I guess that running gcc on 8086 will not be possible (or at least it will
> not be a simple task), the cc1 binary on my i386 is 2MB, and it will not
> be smaller if built for running on 8086. gcc is not a small compiler. The
> point is making a 8086 target for gcc. Running gcc on 8086 is another story,
> and I guess that is almost impossible. (and not worth, at least for me)
>
I supposed so. gcc is bloatware for elks. Even "vi" is :-PPP
> The issue about running a compiler in a 8086 is that it is too
> small. Running a good compiler and development environment on such small
> hardware is not easy, and if we choose go this way, we should choose
> leaving away other things that we would like, including gcc-8086. If we
> choose that all development environment neede to build elks should run
> on 8086, too, we will have additional limitations, and we will need first:
>
> 1. Create a good development environment that runs on elks (we don't
> have it). This environment will have all limitations that the 8086
> hardware will impose to us
> 2. Make elks build using it
>
> IMHO, this would be almost impossible.
>
Minix's ACK does so. Of course, it imposes limitations to the programs
(the 64k limit), but is good enough for many applications. I heard
something about ACK sources... did they free them?
Regards,
--
Javier Sedano Jarillo: javier.sedano@agora-2000.com
(http://www.it.uc3m.es/~jsedano)
Agora Systems, S.A.
C/Aravaca 12
E-28040 Madrid (Spain)
Tel.: +34 91 533 58 57
Fax.: +34 91 534 84 77
--------
do computers dream of electric penguins?
next prev parent reply other threads:[~2004-05-20 17:30 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-19 20:55 Future of ELKS Miguel Bolanos
2004-05-20 3:39 ` I'm in Void
2004-05-20 14:47 ` Miguel Bolanos
2004-05-20 11:42 ` Javier Sedano
2004-05-20 15:15 ` Miguel Bolanos
2004-05-20 15:37 ` Eduardo Pereira Habkost
2004-05-20 16:06 ` Andrey Romanenko
2004-05-21 5:51 ` Dan Olson
2004-05-20 17:30 ` Javier Sedano [this message]
2004-05-21 8:32 ` Gábor Lénárt
2004-05-21 14:15 ` Jody
2004-05-24 9:29 ` Gábor Lénárt
2004-05-24 18:20 ` Alan Cox
2004-05-20 23:43 ` David Given
2004-05-21 1:04 ` Stefan de Konink
2004-05-21 3:39 ` Chad Page
2004-05-29 16:58 ` Gregg C Levine
2004-05-21 5:55 ` Dan Olson
2004-05-21 6:08 ` Jody
2004-05-21 13:24 ` Eduardo Pereira Habkost
2004-05-21 16:30 ` David Given
2004-05-21 16:59 ` Michael McConnell
2004-05-22 12:12 ` David Given
2004-05-22 17:29 ` Chad Page
2004-05-21 18:38 ` Jody
2004-05-22 8:53 ` jb1
2004-05-22 17:00 ` Chad Page
2004-05-24 9:42 ` Gábor Lénárt
2004-05-20 16:54 ` Javier Sedano
2004-05-21 5:50 ` Dan Olson
2004-05-21 9:08 ` Arnaldo Carvalho de Melo
2004-05-21 10:24 ` Alan Cox
2004-05-24 12:20 ` Gábor Lénárt
-- strict thread matches above, loose matches on Subject: below --
2004-05-20 13:40 Pat Gilliland
2004-05-21 17:53 ` Miguel Bolanos
2004-05-20 20:18 Tommy McCabe
2004-05-24 13:17 BODRATO Stefano
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=40ACEB23.7010101@agora-2000.com \
--to=javier.sedano@agora-2000.com \
--cc=ehabkost@conectiva.com.br \
--cc=linux-8086@vger.kernel.org \
--cc=mike@linuxlabs.com \
/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