From: "Christopher C. Chimelis" <chris@debian.org>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: binutils@sources.redhat.com, Hans-Peter Nilsson <hp@bitrange.com>,
"H . J . Lu" <hjl@lucon.org>
Subject: Re: Release 2.12
Date: Thu, 25 Oct 2001 05:09:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.21.0110250805190.16599-100000@spawn.hockeyfiend.com> (raw)
In-Reply-To: <20011024231041.A10694@nevyn.them.org>
On Wed, 24 Oct 2001, Daniel Jacobowitz wrote:
> Yes, that part. And it's certainly not "most". Consider:
> - Debian uses them. That's Chris C.'s decision, and seems to be a
> reasonable one, overall.
I evaluate both the FSF releases and H.J.'s, no matter what. Mostly, I
use H.J.'s for two reasons: includes the hooks for Compaq demangler
support for their compiler releases for Alpha-Linux and also because
H.J.'s usually include newer fixes from CVS for platforms that Debian has
ports for (such as IA-64, HPPA, and MIPS{el}).
> Because critical bugs are found in the released versions and not fixed.
> GNU Libc, for instance, has an unpleasant habit of depending on
> binutils not-yet-released. The patches don't tend to be easily
> back-portable for those without a history of binutils experience. If
> we want to make new programs work, we need to move forward fairly
> frequently, and HJ offers the only way to do that.
Agreed on all points.
C
next prev parent reply other threads:[~2001-10-25 5:09 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-24 18:26 Hans-Peter Nilsson
2001-10-24 18:38 ` Alan Modra
2001-10-24 18:43 ` David O'Brien
2001-10-24 19:30 ` Alan Modra
2001-10-24 19:35 ` MMIX (was: Re: Release 2.12) Hans-Peter Nilsson
2001-10-24 21:45 ` Release 2.12 Eric Christopher
2001-10-25 8:41 ` H . J . Lu
2001-10-25 8:47 ` H . J . Lu
2001-10-24 18:49 ` Daniel Jacobowitz
2001-10-24 19:43 ` Alan Modra
2001-10-24 20:10 ` Daniel Jacobowitz
2001-10-24 20:35 ` Alan Modra
2001-10-24 20:44 ` Daniel Jacobowitz
2001-10-25 5:09 ` Christopher C. Chimelis [this message]
2001-10-25 1:56 ` Philip Blundell
2001-10-25 8:30 ` H . J . Lu
2001-10-25 8:47 ` David O'Brien
[not found] ` <amodra@bigpond.net.au>
2002-01-04 17:42 ` [Linux-ia64] Compiling kernel 2.4.17 fails at link stage Grant Grundler
2002-01-04 17:59 ` H . J . Lu
2002-01-04 20:37 ` Grant Grundler
2002-01-04 22:39 ` H . J . Lu
2002-01-07 12:52 ` Grant Grundler
2002-01-04 19:21 ` Alan Modra
2003-11-29 2:33 ` ppc problem with .rodata.str1.4. binutils requirement for gcc 3.3.1? David Edelsohn
2003-11-29 3:05 ` Alan Modra
2003-11-29 4:06 ` David Edelsohn
2003-11-29 4:10 ` Andrew Pinski
2003-11-29 4:20 ` David Edelsohn
2003-11-29 6:47 ` Alan Modra
2003-11-29 19:40 ` David Edelsohn
2004-05-19 15:19 ` Powerpc Linux build fails David Edelsohn
2004-05-20 0:39 ` Alan Modra
2004-05-20 1:24 ` Alan Modra
2004-05-20 1:46 ` Alan Modra
2004-05-20 2:29 ` David Edelsohn
2004-05-20 3:10 ` Alan Modra
2006-08-04 1:49 ` Link problems with section anchors David Edelsohn
2006-08-04 2:04 ` Alan Modra
2001-10-24 19:37 ` Release 2.12 Russ Allbery
2001-10-24 19:52 ` Alan Modra
2001-10-25 0:46 ` H . J . Lu
2001-10-25 8:57 ` David O'Brien
2001-10-25 9:38 ` H . J . Lu
2001-10-25 9:44 ` H . J . Lu
2001-12-31 19:09 Compiling kernel 2.4.17 fails at link stage Krishnakumar B
2002-01-04 3:50 ` Alan Modra
2002-01-04 12:39 ` [Linux-ia64] " Alan Modra
[not found] <087e01c3b5da$77d658e0$0202040a@catdog>
2003-11-29 1:42 ` ppc problem with .rodata.str1.4. binutils requirement for gcc 3.3.1? Alan Modra
2003-11-29 18:14 ` Kris Warkentin
[not found] <3A3FC75F7C72D711A7DC009027AC9C4B1788D9@jupiter>
2004-05-19 3:30 ` Powerpc Linux build fails Alan Modra
2004-05-19 4:27 ` Geoff Keating
2004-05-19 5:10 ` Alan Modra
2004-05-19 16:24 ` Kumar Gala
2004-05-20 0:44 ` Alan Modra
[not found] <44D2755E.9020600@us.ibm.com>
2006-08-04 1:30 ` Link problems with section anchors Alan Modra
2006-08-04 9:04 ` Richard Sandiford
2006-08-04 13:53 ` Steven Munroe
2006-08-04 13:54 ` David Edelsohn
2006-08-04 14:01 ` Richard Sandiford
2006-08-04 14:12 ` David Edelsohn
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.LNX.4.21.0110250805190.16599-100000@spawn.hockeyfiend.com \
--to=chris@debian.org \
--cc=binutils@sources.redhat.com \
--cc=drow@mvista.com \
--cc=hjl@lucon.org \
--cc=hp@bitrange.com \
/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).