From: Juan Perez-Sanchez <lithoxs@gmail.com>
To: linux-8086 <linux-8086@vger.kernel.org>
Subject: Re: Patch set to ease replacement of BCC compiler
Date: Thu, 21 May 2015 09:13:47 -0500 [thread overview]
Message-ID: <CAD6VGuarU=Q2jaAMJBdM76h5A7fAN6ENvd0_ptdyiMWm0Kzv0Q@mail.gmail.com> (raw)
In-Reply-To: <20150521062324.GN8197@example.net>
On Thu, May 21, 2015 at 1:23 AM, <u-vpoa@aetey.se> wrote:
>
>> The compilers considered are open-watcom
>> and ia16-unknown-elks-gcc.
>
> We should keep in mind that open-watcom has a minefield license.
> One ought to be careful to not introduce any dependency on it.
>
> Juan, wonder if you tried/considered Coherent C compiler?
>
No, and the reason is that I don't have any idea of how much work is
needed to make it functional under linux.
Another candidate is TACK, many times proposed in this list. It would
be nice to have staticly linked binaries for linux available.
Juan
next prev parent reply other threads:[~2015-05-21 14:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 5:47 Patch set to ease replacement of BCC compiler Juan Perez-Sanchez
2015-05-21 6:23 ` u-vpoa
2015-05-21 14:13 ` Juan Perez-Sanchez [this message]
2015-05-21 6:27 ` u-vpoa
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='CAD6VGuarU=Q2jaAMJBdM76h5A7fAN6ENvd0_ptdyiMWm0Kzv0Q@mail.gmail.com' \
--to=lithoxs@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).