From: Paul Nasrat <pauln@truemesh.com>
To: ELKS <Linux-8086@Vger.Kernel.Org>
Subject: Re: New version of Bob's C compiler
Date: Wed, 24 Jul 2002 23:34:32 +0100 [thread overview]
Message-ID: <20020724223432.GB7170@raq465.uk2net.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0207242313290.30515-100000@Consulate.UFP.CX>
On Wed, Jul 24, 2002 at 11:15:48PM +0100, Riley Williams wrote:
> Hi Gregg.
>
> > Go ahead folks and send me flaming mail off list, but here goes.
> > If a new one has been posted to his page, then will it be mirrored
> > anywhere on the general ELKS pages, and FTP sites?
>
> Who wants to conduct a poll to decide whether this is a good or bad
> idea? I can see viewpoints both ways...
>
> FOR: Much of ELKS becomes simpler with the latest facilities.
>
> AGIN: ELKS becomes dependent on having the latest BCC compiler.
True, elks should be still compilable on the common distro Dev86
package. However, I will go and package up both a Mandrake style and
RedHat stye rpm and be happy to submit those to all, if we can encourage
package maintainers to update then it's not too nasty to ask ppl who
compile from source to ensure they are using a recent edition.
By the looks of it Debian unstable is on 0.16.3 anyway so are probably
keeping an eye out on Robert's page.
Maybe we should say the next major release of Elks will require a recent
Dev86, and concentrate on helping distro's get the most recent Dev86 and
dosemu and elksemu happily working. Then we can try and clean up the
code based on new compiler features.
BTW, I think things are broken for SIBO atm, need to fix but need
time...
Paul
next prev parent reply other threads:[~2002-07-24 22:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-24 22:08 New version of Bob's C compiler Gregg C Levine
2002-07-24 22:15 ` Riley Williams
2002-07-24 22:34 ` Paul Nasrat [this message]
2002-07-25 5:59 ` Riley Williams
2002-07-25 7:15 ` Paul Nasrat
2002-07-25 8:09 ` Harry Kalogirou
2002-07-25 19:28 ` Blaz Antonic
2002-07-25 16:38 ` Manuel Novoa III
2002-07-25 19:56 ` Riley Williams
2002-07-25 20:36 ` Manuel Novoa III
2002-07-26 18:27 ` Harry Kalogirou
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=20020724223432.GB7170@raq465.uk2net.com \
--to=pauln@truemesh.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