Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Klee Dienes <klee@apple.com>
To: Ian Lance Taylor <ian@airs.com>
Cc: binutils@sources.redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [RFC] Update to current automake/autoconf/libtool versions.
Date: Thu, 05 Dec 2002 14:29:00 -0000	[thread overview]
Message-ID: <08402FC0-08A1-11D7-A7CE-00039396EEB8@apple.com> (raw)
In-Reply-To: <m3u1hskyd3.fsf@gossamer.airs.com>

Sure, but is it really a common situation where we are neither able to 
revert to a previous released version of libtool, or get a release of 
the upstream tools made with the needed fix in a timely fashion?

[ Here I wake up from my optimistic reverie and proceed to answer my 
own rhetorical question: ]

The answer to this, of course, is "yes," and I agree that poor 
backwards compatibility from autoconf-2.13 to autoconf-2.50 is the real 
source of the problem here.  My point is that the current solution 
doesn't seem to be addressing the real problem --- we have essentially 
created our own forked versions of all of the autotools, with no 
visible plans to re-merge to the FSF version, and no intent to maintain 
the forked version on our own.

I'm not arguing that it will never be necessary to fork our own version 
of autotools in the case of a short-term emergency (well actually, I 
might argue that, but I'm not arguing it here).  I'm just arguing that 
a forked version of binutils with no clear upstream referent is a 
particularly bad state of affairs:

	-rw-r--r--   1 77       1002       259210 Feb 27  2000 
autoconf-000227.tar.bz2
	-rw-r--r--   1 77       1002       292827 Feb 27  2000 
automake-000227.tar.bz2
	-rw-r--r--   1 77       1002       519132 Feb 27  2000 
gettext-000227.tar.bz2
	-rw-r--r--   1 77       1002       370603 Feb 27  2000 
libtool-000227.tar.bz2


On Thursday, December 5, 2002, at 03:24 PM, Ian Lance Taylor wrote:

> Klee Dienes <klee@apple.com> writes:
>
>> As long as the versions of the tools are specified by a version string
>> referencing an official version in README-maintainer-mode, and not by
>> "whatever version is on sourceware.cygnus.com", I'm happy.
>
> That works until there is a bug which is a problem for the binutils
> but there is not yet a new release.
>
> It's not a theoretical point.  That's the reason we started using
> versions stored on sources.redhat.com in the first place.
>
> Ian


  reply	other threads:[~2002-12-05 22:29 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-13  8:55 [RFA/PATCH] Darwin fixes for ltconfig, ltcf-c.sh Klee Dienes
2002-11-13  9:57 ` Andrew Cagney
2002-11-13 10:32   ` Klee Dienes
2002-12-04 22:04     ` [RFC] Update to current automake/autoconf/libtool versions Klee Dienes
2002-12-05  5:26       ` Hans-Peter Nilsson
2002-12-05 14:07         ` Alan Modra
2002-12-05  7:43       ` Andrew Cagney
2002-12-05  8:22         ` Klee Dienes
2002-12-05  9:01           ` Andrew Cagney
2002-12-05 12:55             ` Klee Dienes
2002-12-05 13:03               ` Daniel Jacobowitz
2002-12-05 13:13                 ` Andrew Cagney
2002-12-05 13:16                   ` Daniel Jacobowitz
2002-12-05 13:08               ` Andrew Cagney
2002-12-05 13:18                 ` Klee Dienes
2002-12-05  8:28         ` DJ Delorie
2002-12-05  9:37           ` Klee Dienes
2002-12-05  9:42             ` DJ Delorie
2002-12-05 10:28               ` Klee Dienes
2002-12-05  9:31         ` H. J. Lu
2002-12-05  7:44       ` Maciej W. Rozycki
2002-12-05  9:01         ` Klee Dienes
2002-12-05  8:09       ` Daniel Jacobowitz
2002-12-05  8:29         ` DJ Delorie
2002-12-05  8:35           ` Daniel Jacobowitz
2002-12-05  8:37             ` DJ Delorie
2002-12-05  8:40             ` Maciej W. Rozycki
2002-12-05  8:44               ` Daniel Jacobowitz
2002-12-05  9:19                 ` Elena Zannoni
2002-12-05  9:54                 ` Klee Dienes
2002-12-05 10:10                   ` Maciej W. Rozycki
2002-12-05 10:59                   ` Andrew Cagney
2002-12-06  5:52                     ` Maciej W. Rozycki
2002-12-05 10:59                   ` Doug Evans
2002-12-05 12:11                     ` Klee Dienes
2002-12-05 12:23                       ` Ian Lance Taylor
2002-12-05 14:29                         ` Klee Dienes [this message]
2002-12-06  5:34                     ` Maciej W. Rozycki
2002-12-06  7:25                       ` DJ Delorie
2002-12-06  8:06                         ` Maciej W. Rozycki
2002-12-06  8:47                           ` DJ Delorie
2002-12-05 13:59                   ` Ben Elliston
2002-12-05 13:41                     ` Ben Elliston
2002-12-30 16:10       ` Alexandre Oliva
2002-12-05 10:15 Michael Elizabeth Chastain
2002-12-05 10:37 ` Klee Dienes
2002-12-05 11:08 Nathanael Nerode
2002-12-05 11:31 ` Andrew Cagney
2002-12-05 13:31 ` Zack Weinberg
2002-12-05 14:36   ` Alan Modra
2002-12-05 14:56     ` Ian Lance Taylor
2002-12-05 15:22       ` Alan Modra
2002-12-05 15:43         ` Ian Lance Taylor
2002-12-05 15:51           ` Andrew Cagney
2002-12-05 15:47         ` Mike Stump
2002-12-05 16:30           ` Alan Modra
2002-12-05 16:45             ` Zack Weinberg
2002-12-08  2:49         ` Klee Dienes
2002-12-05 14:29 ` Christopher Faylor
2002-12-06  6:45 ` Maciej W. Rozycki
2002-12-08 10:53 ` Klee Dienes
2002-12-05 14:40 Nathanael Nerode
2002-12-05 15:19 ` Zack Weinberg
2002-12-06 10:21   ` Tom Tromey
2002-12-07 13:06   ` Alexandre Oliva
2002-12-07 16:03     ` Zack Weinberg
2002-12-09 19:16       ` Alexandre Oliva
2002-12-09 21:52         ` Geoff Keating
2002-12-08 13:11     ` Tom Tromey
2002-12-05 14:42 Joern Rennecke
2002-12-06  5:28 Nathanael Nerode
     [not found] <9A4230D6-1D26-11D7-BFCA-00039396EEB8@apple.com>
2003-01-12 13:22 ` Alexandre Oliva

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=08402FC0-08A1-11D7-A7CE-00039396EEB8@apple.com \
    --to=klee@apple.com \
    --cc=binutils@sources.redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=ian@airs.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