public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: Harry Kalogirou <harkal@gmx.net>
To: Riley Williams <Riley@Williams.Name>
Cc: Manuel Novoa III <mjn3@codepoet.org>, ELKS <Linux-8086@Vger.Kernel.Org>
Subject: Re: New version of Bob's C compiler
Date: 26 Jul 2002 21:27:59 +0300	[thread overview]
Message-ID: <1027690883.1191.21.camel@cool> (raw)
In-Reply-To: <Pine.LNX.4.21.0207252036400.30515-100000@Consulate.UFP.CX>

Την Πεμ, 25-07-2002 στις 22:56, ο/η Riley Williams έγραψε:

> >> AGAINST: ELKS becomes dependent on having the latest BCC compiler.
> 
> > Is this really much of a drawback? Building bcc isn't that big
> > an issue.
> 
> Are you willing to be the one to deal with all the "ELKS doesn't
> compile" spam that will result from the people who download ELKS onto
> their system, then try to compile it and it throws up lots of error
> messages simply because they have an old version of BCC installed and
> we rely on a new version with lots of enhancements not in the commonly
> installed versions?

A simple BCC version check at the begining of compilation, will solve
all the problems. And for sure the BCC version check is going be much
smaller that this thread in lines.
 
> I'm not - I had enough of that from HarKal when ELKS was sensitive to
> a difference between his system configuration and mine with the result
> that it compiled here but not on his system. We sorted that out a while
> back and removed the said sensitivity from ELKS, but this will bring in
> far more sensitivities than I'm willing to deal with.

Requiring a specific version of some kind of tool is one thing and
requiring specific system configuration is an other. I beleave that we
can safely use the latest compiler; The one that will like to compile
from source, will find a way to get tha compiler.

Harry



-
To unsubscribe from this list: send the line "unsubscribe linux-8086" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2002-07-26 18:27 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
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 [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=1027690883.1191.21.camel@cool \
    --to=harkal@gmx.net \
    --cc=Linux-8086@Vger.Kernel.Org \
    --cc=Riley@Williams.Name \
    --cc=mjn3@codepoet.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