public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "H . J . Lu" <hjl@lucon.org>
To: "Joseph S. Myers" <jsm28@cam.ac.uk>
Cc: Joern Rennecke <amylaar@redhat.com>, gcc@gcc.gnu.org
Subject: Re: Compiler for Red Hat Linux 8
Date: Wed, 18 Jul 2001 16:23:00 -0000	[thread overview]
Message-ID: <20010718162315.B19581@lucon.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0107182330050.21466-100000@kern.srcf.societies.cam.ac.uk>

On Wed, Jul 18, 2001 at 11:41:42PM +0100, Joseph S. Myers wrote:
> 
> If the Red Hat 8 GCC version were based off a GNUpro version, but that
> version were checked in to the FSF repository on a branch, that might at
> least help people trying to respond helpfully to misdirected bug reports
> and questions work out what is in Red Hat's release - as well as avoiding
> wasting people's time on the "seek out GNUpro releases on the net" game
> <URL: http://gcc.gnu.org/ml/gcc/2001-03/msg00660.html >.

Has anyone ever noticed most of the Linux vendors can use a *released*
Linux binutils? Has anyone looked at the binutils Red Hat uses? It
has far less patches than the gcc they are using. It is because I have
been making such frequent Linux binutils releases that there is no
need for any Linux vendors to roll their own versions of binutils. If
the current Linux binutils doesn't work, it won't last for more than
2 weeks after I am notified. Forget about the *official* FSF binutils.
I don't think it is usable for Red Hat without serious patches.
Admittedly, gcc is much more complex than binutils. But as long as
people don't make making a release a big deal, I don't see why more
frequent bug releases can't be made. They may not be as polished as
we'd like to be. But at least, there is a chance that Red Hat 8 may use
a *relaased* gcc.


H.J.

  reply	other threads:[~2001-07-18 16:23 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-17 13:04 Geoff Keating
2001-07-17 15:52 ` Joe Buck
2001-07-17 17:48   ` Per Bothner
2001-07-18  8:55     ` Joseph S. Myers
2001-07-17 18:24 ` Craig Rodrigues
2001-07-18  2:41 ` Andreas Jaeger
2001-07-18  9:03   ` H . J . Lu
2001-07-18 12:01     ` Joe Buck
2001-07-18 12:46       ` H . J . Lu
2001-07-18 13:22         ` Joe Buck
2001-07-18 13:31           ` H . J . Lu
2001-07-18 14:28             ` David Edelsohn
2001-07-18 15:03               ` Joern Rennecke
2001-07-18 15:12                 ` David Edelsohn
2001-07-18 15:24                   ` Joe Buck
2001-07-18 17:05                     ` H . J . Lu
2001-07-19  4:56                     ` Toon Moene
2001-07-18 15:41                 ` Joseph S. Myers
2001-07-18 16:23                   ` H . J . Lu [this message]
2001-07-18 12:18     ` Sergey Ostrovsky
2001-07-18 15:19       ` Ken Whaley
2001-07-18 15:30         ` Toon Moene
2001-07-18 15:59           ` Ken Whaley
2001-07-18 16:08             ` Toon Moene
2001-07-18 13:30   ` Gerald Pfeifer
2001-07-19  5:17     ` Andreas Jaeger
2001-07-19 12:23       ` Gerald Pfeifer
2001-07-18 19:07   ` LinuxVN
2001-07-18 13:44 ` Toon Moene
2001-07-17 17:37 mike stump
2001-07-17 20:00 Benjamin Kosnik
2001-07-18 13:21 Benjamin Kosnik
2001-07-18 14:33 Geoff Keating
2001-07-18 14:41 dewar
2001-07-18 15:29 ` Geoff Keating
2001-07-18 17:50   ` Joe Buck
2001-07-18 18:59 ` Michael Eager
2001-07-18 19:26   ` Justin Guyett
2001-07-19  9:05     ` Mark Mitchell
2001-07-19 19:28   ` akbar A.
2001-07-18 22:10 ` Per Bothner
2001-07-18 22:19   ` Joe Buck
2001-07-18 22:38     ` Per Bothner
2001-07-18 23:00       ` Alex Rosenberg
2001-07-19 14:05       ` Jonathan Larmour
2001-07-18 20:02 dewar
2001-07-19  0:29 Bernard Dautrevaux
2001-07-19  1:16 ` Toon Moene
2001-07-19  1:36 Bernard Dautrevaux
2001-07-19  2:40 ` Joseph S. Myers
2001-07-19  3:02 ` Roman Zippel
2001-07-19  3:12 ` Russ Allbery
2001-07-19  4:33 dewar
2001-07-19 10:49 dewar
2001-07-19 23:16 Bernard Dautrevaux

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=20010718162315.B19581@lucon.org \
    --to=hjl@lucon.org \
    --cc=amylaar@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jsm28@cam.ac.uk \
    /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).