From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Given Subject: Re: Right BCC version to use ? Date: Tue, 24 Mar 2015 22:50:42 +0100 Message-ID: <5511DC32.70701@cowlark.com> References: <55110CCF.9000705@gmail.com> <0866EC18-C072-429D-875E-BBFF5E85F6C7@jodybruchon.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="dVBSxIM5hMcm0lsO8VQXSpCj3oH3dlnqk" Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type; bh=sJ9Ovyy6t1r6e9GQSfrGfi43okzuZFIAyQRLAu5S1Ns=; b=BhzoTPLjNFH+eaKqvDFnUd16wNuIhfT9FmW25jIdUTfgbZZm8+JiWoDrphHDMSi9l1 zyUWMMH/WVQFVIhyQ//7gtdNM5HH63lQzTB7yaWo6wVFuk0b8afb/jNrRlITpTsFQSrg /Vpe44B+r2A+hzOEXxoYH+627e2Nk+AF4uMGckzIl4z3q4MbsPRYZt5BMv7w+FdwQDiU 0TXyAdoCCdgQjC4IuLOhy8LzztFwn+Dcr5fKCqyVzS8stXXCjXmrMzvrGX+Q+xx80FGx jTv9Q9sM47QCQgGUBVzKxUyktRSioG7VLEW1V/XPgRMlE6eaLx0ebwieuesvd2LeCNN7 dqJw== In-Reply-To: <0866EC18-C072-429D-875E-BBFF5E85F6C7@jodybruchon.com> Sender: linux-8086-owner@vger.kernel.org List-ID: To: Jody Bruchon , linux-8086@vger.kernel.org This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --dVBSxIM5hMcm0lsO8VQXSpCj3oH3dlnqk Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 24/03/15 12:30, Jody Bruchon wrote: [...] > ELKS is tightly tied to BCC for now, so some future development will pr= obably require changes to it. A big difference between BCC and GCC is tha= t BCC includes a C library and headers whereas GCC is only a compiler and= requires a C library to be built separately. That means I can't fix issu= es with the C library without bringing the whole thing along. While I wouldn't suggest it for *new* development, because the compiler technology is old and clunky and rather unmaintainable, but the ACK is an ANSI C compiler suite which supports 8086 and comes with a full libc --- this is what Minix used. It's even theoretically possible to run it self-hosted on an ELKS-style machine, although it'd take work to recover that ability these days. The 8086 coded generate isn't too bad. (Minix was developed with it, after all.) The downside is that it lives in its own little universe and doesn't interoperate with anything; you have to use the ACK object file format and the ACK linker etc. I believe it already supports Minix 16/16 segmented binaries. The effort needed to persuade the ACK to produce ELKS executables is probably quite small --- it already has partial support for ix86 and m68k Linux; how different is the ELKS system call model? Making it build the kernel is probably harder due to different dev86 and ACK linker magic= =2E This would only be worthwhile as a stopgap until 8086 gcc or pcc is available, and it would need some careful evaluation of the code quality, but it might be worth looking into. The fairly elderly website is at: http://tack.sourceforge.net/ --=20 =E2=94=8C=E2=94=80=E2=94=80=E2=94=80 =EF=BD=84=EF=BD=87=EF=BC=A0=EF=BD=83= =EF=BD=8F=EF=BD=97=EF=BD=8C=EF=BD=81=EF=BD=92=EF=BD=8B=EF=BC=8E=EF=BD=83=EF= =BD=8F=EF=BD=8D =E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80 http://www.= cowlark.com =E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80 =E2=94=82 =E2=94=82 "Sufficiently advanced incompetence is indistinguishable from =E2=94=82 malice." -- Vernon Schryver --dVBSxIM5hMcm0lsO8VQXSpCj3oH3dlnqk Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIVAwUBVRHcNXTPe2DYoi4EAQpJqQ//SEVTkxi7g8Q5ZY8hXB9/smTAkcDzK7h3 B4Ui+utletVKVU57i1E0WmoGxUXd4Qk6dW5jUVubMjFvvHfC9LLN8qpkQPSyshbh /SPujgGX4bsZb3t49lM75DaBtXV0Kz19GR8pQFJE2mPIBOG/bbjP/mX+mHCiwart OiwYpOJxGik16m3Z9Q9vCAVL+dF9oOY6OxCdBEw8/4YKLghByKHESX0tCLTJlSaq Kmbs7gaIYJ5mwOAapNGwrVCdfFsCKsKrsAWdGKKIIXYqFRUIkRFyqYbFw/7Valze JPFCb+aG3Smwx3FQXSWAGuOPPw3SIoKn8ZPZU2bsayQ9hVPkierMgayv6yYJrFhh lbbasCnDJ0BuC9V2ZXHHsEONZP4UgBA+bdLTjeFpdPkMj2Ok9501Se1518FrbulA o3KHlIvPDQcWgOdHRDpR8yRis/zGP7iyS6y9QOZF++eA/PQPKMy9omCANYoA4Fgd V5nttqK4qpsC34b7DCS4meUU5w1lifAnnd67vQG2lmlTPGA/OdWXaXjk0QohfLmI 71S8SCNCQDnXpXS5zW23tqGQHrbJXzSpr+HGmH19vcUIPaBhh9RJQzJTA/YAe+rZ n1mcvmq5xem9SrIsbBPsTJ+oUg+GdLbneWotsgMbrsVh0bKK4Vsasi4r4bcA86ib Fd9OGVp5mO8= =Bsuc -----END PGP SIGNATURE----- --dVBSxIM5hMcm0lsO8VQXSpCj3oH3dlnqk--