From: Andrew Cagney <ac131313@redhat.com>
To: Zack Weinberg <zack@codesourcery.com>
Cc: gcc@gcc.gnu.org, binutils@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: Updating to Autoconf 2.5x
Date: Mon, 09 Jun 2003 21:05:00 -0000 [thread overview]
Message-ID: <3EE4F6AD.7060300@redhat.com> (raw)
In-Reply-To: <87of17t2j4.fsf@egil.codesourcery.com>
> As you all know, the configure scripts for GCC, GDB, and binutils must
> be generated with autoconf 2.13.
GDB and BINUTILS use autoconf 000227 and not 2.13.
> thoroughly obsolete, to the point where recent releases of popular
> free operating systems may not ship it at all. It is thus becoming
> increasingly difficult to maintain these scripts. Furthermore, using
> this old version of autoconf forces us to continue using old versions
> of automake and libtool as well. At the recent GCC summit it was
> agreed that we
I guess the royal ``we'' here is GCC?
Fortunatly GDB (binutils?) also see a need to get off the current
autoconf and as such, I personally welcome this move.
How does nathaniel and dj's work fit into this - its kind of a logical
next step.
> need to make a concerted effort and migrate to autoconf
> 2.5x. Exactly how we're going to do that, however, has not yet been
> decided.
>
> I have created a mailing list for discussing this issue in detail,
> making plans, and implementing them. All interested parties are
> invited to subscribe. I don't intend this to be a long-lived list;
> I hope we can get this conversion done in under a month.
>
> List address: autoconf-conversion@codesourcery.com
> Subscribe: autoconf-conversion-subscribe@codesourcery.com (ezmlm)
> Archives: http://www.codesourcery.com/archives/autoconf-conversion/maillist.html
I think it would be better if this list was hosted, and made part of
gcc.gnu.org.
Andrew
next prev parent reply other threads:[~2003-06-09 21:05 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-09 20:32 Zack Weinberg
2003-06-09 21:05 ` Andrew Cagney [this message]
2003-06-09 21:09 ` Christopher Faylor
2003-06-09 22:58 ` Alexandre Oliva
2003-06-09 23:06 ` Daniel Jacobowitz
2003-06-09 23:38 ` Joe Buck
2003-06-09 23:48 ` DJ Delorie
2003-06-10 0:33 ` Joe Buck
2003-06-10 4:40 ` Zack Weinberg
2003-06-10 6:42 ` Mark Mitchell
2003-06-10 9:25 ` Joseph S. Myers
2003-06-10 14:24 ` Christopher Faylor
2003-06-10 15:57 ` Mark Mitchell
2003-06-10 16:40 ` Christopher Faylor
2003-06-12 4:16 ` Red Hat logos on FSF web pages (was Re: Updating to Autoconf 2.5x) Christopher Faylor
2003-06-10 17:40 ` Updating to Autoconf 2.5x Andrew Cagney
2003-06-10 13:48 ` Kaveh R. Ghazi
2003-06-10 14:23 ` Christopher Faylor
2003-06-10 14:30 ` Daniel Jacobowitz
2003-06-10 15:44 ` Andrew Cagney
2003-06-10 16:03 ` Mark Mitchell
2003-06-10 17:47 ` Joe Buck
2003-06-09 23:58 ` Daniel Jacobowitz
2003-06-10 0:50 ` Alexandre Oliva
2003-06-10 0:55 ` DJ Delorie
2003-06-10 2:58 ` Christopher Faylor
2003-06-10 3:43 ` Ian Lance Taylor
2003-06-10 2:37 ` Christopher Faylor, Christopher Faylor
2003-06-09 21:15 ` DJ Delorie
2003-06-09 23:01 ` 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=3EE4F6AD.7060300@redhat.com \
--to=ac131313@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=zack@codesourcery.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).