From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Given <dg@cowlark.com>
Subject: Re: ACK ANSI C compiler
Date: Wed, 17 Aug 2005 00:56:15 +0100
Message-ID: <200508170056.16047.dg@cowlark.com>
References: <200508151712.57698.dg@cowlark.com> <123f01c5a1ce$32c01070$6502a8c0@dionysus> <1124218178.3131.12.camel@cool>
Mime-Version: 1.0
Content-Type: multipart/signed;
  boundary="nextPart2438633.HTRcGQtDrS";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Return-path: <linux-8086-owner@vger.kernel.org>
In-Reply-To: <1124218178.3131.12.camel@cool>
Sender: linux-8086-owner@vger.kernel.org
List-Id: <linux-8086.vger.kernel.org>
To: linux-8086@vger.kernel.org

--nextPart2438633.HTRcGQtDrS
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Tuesday 16 August 2005 19:49, Harry Kalogirou wrote:
> > Does ACK compiles ELKS
>
> No it doesn't. Actually it is going to be a nightmare to make it compile
> under
> ACK. But we probably should face the daemons...

Apart from inline assembly, the biggest problem would most likely be=20
generating the output binaries: the ACK's linker won't generate output file=
s.=20
Instead, the linker (it's called led) produces ack.out format files, just=20
like any other object file, and relies on an architecture specific program =
to=20
convert them into executable binaries.

(Given the vast number of different output formats, this is entirely=20
reasonable, if a little unhelpful.)

=46or ELKS, you'd probably have to write two binary converters: one for the=
=20
kernel, and one for the executables themselves. Neither of these would be=20
particularly difficult, especially since ELKS binaries are heavily based on=
=20
Minix binaries, and of course a Minix converter is supplied.=20
(arch/i86/cv/cv.c if anyone's interested.)

=2D-=20
"Curses! Foiled by the chilled dairy treats of righteousness!" --- Earthwor=
m=20
Jim (evil)

--nextPart2438633.HTRcGQtDrS
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQBDAn0gf9E0noFvlzgRAh5dAKCDc0D7BLzoN8brCQeSu9hAqtvzbwCdGHCb
RHfjOfnIQS3nzcHwxm1wryU=
=+PgF
-----END PGP SIGNATURE-----

--nextPart2438633.HTRcGQtDrS--