This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [RFC] Update to current automake/autoconf/libtool versions.
- From: Klee Dienes <klee at apple dot com>
- To: Daniel Jacobowitz <drow at mvista dot com>
- Cc: "Maciej W. Rozycki" <macro at ds2 dot pg dot gda dot pl>,DJ Delorie <dj at delorie dot com>,ac131313 at redhat dot com,binutils at sources dot redhat dot com,gdb-patches at sources dot redhat dot com
- Date: Thu, 5 Dec 2002 12:54:48 -0500
- Subject: Re: [RFC] Update to current automake/autoconf/libtool versions.
I actually found the files in ftp://sources.redhat.com/pub/binutils to
be an impediment to using the correct versions. For a long time I had
no idea they even existed, and then once I found out about them, it was
even more confusing, since they weren't the versions that were actually
used.
I'd argue that we should:
1) Specify the versions of autoconf/automake/libtool/gettext by
reference to official tarballs from ftp.gnu.org. In general, define
the version used to be "the most recent officially released version of
each tool".
and either
2a) Consider updates to generated files caused by re-configuring with
the most recent released version of the tools as an "obvious fix".
or (even better)
2b) Configure the CVS repository to run autoreconf using the most
recent versions whenever a new configure.in/Makefile.in/Makefile.am is
committed.
The idea here is that it's relatively straightforward for a
binutils/gdb maintainer to know what to do when updating a
configuration file (get the most recent version of the tools from the
FSF and use them), and that we have a natural tendency to stay
up-to-date with automake/autoconf changes, without having flag-day
style upgrades become an issue.
On Thu, Dec 05, 2002 at 05:39:54PM +0100, Maciej W. Rozycki wrote:
They're in ftp://sources.redhat.com/pub/binutils/ already. Have been
for years.