public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Robert Lipe <robertlipe@usa.net>
Cc: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>, <gcc@gcc.gnu.org>
Subject: Re: sun/os as release candidate was: Removal of V2 code
Date: Mon, 20 Nov 2000 17:59:00 -0000	[thread overview]
Message-ID: <Pine.BSF.4.30.0011210255280.89188-100000@deneb.dbai.tuwien.ac.at> (raw)
In-Reply-To: <20001120114731.F9451@rjlhome.sco.com>

On Mon, 20 Nov 2000, Robert Lipe wrote:
> Someone that cares about K&R could step up to the plate to add a cron
> job to do a nightly (or whatever) build on such a system.

Exactly. And if there's none left who cares about K&R, well, than at some
point in the future we should decide that this requirement will go away.

> Does anyone other than HP even still provide a K&R-only compiler?  If
> so, since there are binary kits of GCC available for that target, has
> the time come for us to relax the K&R restriction for bootstrapping GCC
> completely?

Personally, I wouldn't mind very much... (But we shouldn't do this
lightly and really check that no platforms in use break.)

Gerald
-- 
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/

  reply	other threads:[~2000-11-20 17:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-20  8:55 Kaveh R. Ghazi
2000-11-20  9:46 ` sun/os as release candidate was: " Robert Lipe
2000-11-20 17:59   ` Gerald Pfeifer [this message]
2000-11-20  9:47 ` law
2000-11-20 12:53 sun/os as release candidate was: " Kaveh R. Ghazi
2000-11-20 13:41 ` Zack Weinberg

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=Pine.BSF.4.30.0011210255280.89188-100000@deneb.dbai.tuwien.ac.at \
    --to=pfeifer@dbai.tuwien.ac.at \
    --cc=gcc@gcc.gnu.org \
    --cc=ghazi@caip.rutgers.edu \
    --cc=robertlipe@usa.net \
    /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).