public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: David Given <dg@cowlark.com>
To: Linux-8086 <linux-8086@vger.kernel.org>
Subject: Re: Ok lets get back on track
Date: Thu, 04 May 2006 21:14:40 +0100	[thread overview]
Message-ID: <445A60B0.7020705@cowlark.com> (raw)
In-Reply-To: <003501c66fb4$5ab7cff0$6502a8c0@dionysus>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hans wrote:
[...]
> Another suggestion is to use ACK. This has the added advantage that we
> can target different microcontroller/processors something which might
> boost the popularity of ELKS. David Given is working on (or has
> completed? ) resurrecting this compiler. See
> http://www.opensubscriber.com/message/linux-8086@vger.kernel.org/1939852.html
> for a trail of old messages.

Still going; it's a slow, tedious process. I'm currently rewriting the build
system from scratch to make it, like, actually maintainable. This has,
unfortunately, require writing a build tool to do it! It tends to move on in
fits and starts as I gain/lose interest.

However, the version on the website with the old build system
(http://tack.sf.net) *does* build and run on Linux. The only trouble with it
is that it doesn't know how to produce ELKS binaries, so someone would have to
write a binary format converter to do that (and produce an ELKS syscall
library). This wouldn't be much work, seeing as how ELKS uses Minix binaries
which the ACK does know how to make, but would still need someone to actually
do it... volunteers?

(The ACK will, if you ask it to, compile Fortran, Pascal, K&R C, ANSI C,
Occam, Basic and Modula 2 for any platform it supports; so if someone *were*
to do that, you suddenly gain a whole bunch of new supported languages.)

- --
+- David Given --McQ-+ "If you're up against someone more intelligent
|  dg@cowlark.com    | than you are, do something insane and let him think
| (dg@tao-group.com) | himself to death." --- Pyanfar Chanur
+- www.cowlark.com --+
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEWmCwf9E0noFvlzgRAjEBAJ9y+BfNLz8HfHTo/z4E4R8Nn0n/3wCgikzW
RmWuznGhr8wvoOdzuJSSn0Y=
=5P8l
-----END PGP SIGNATURE-----

      reply	other threads:[~2006-05-04 20:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-03 23:45 Ok lets get back on track Fredrik Söderlund
2006-05-04 19:52 ` Hans
2006-05-04 20:14   ` David Given [this message]

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=445A60B0.7020705@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