public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Zack Weinberg <zack@codesourcery.com>
To: Andrew Cagney <ac131313@redhat.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 23:01:00 -0000	[thread overview]
Message-ID: <87fzmiua86.fsf@egil.codesourcery.com> (raw)
In-Reply-To: <3EE4F6AD.7060300@redhat.com> (Andrew Cagney's message of "Mon, 09 Jun 2003 17:05:49 -0400")

Andrew Cagney <ac131313@redhat.com> writes:

>> 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.

I didn't know that; thanks for the clarification.

>> At the recent GCC summit it was agreed that we
>
> I guess the royal ``we'' here is GCC?

Quite a few binutils and GDB maintainers were present at the
discussion I am referring to, and they agreed as well.

> Fortunatly GDB (binutils?) also see a need to get off the current
> autoconf and as such, I personally welcome this move.

Glad to have you on board.

> How does nathaniel and dj's work fit into this - its kind of a logical
> next step.

Good question.  

> I think it would be better if this list was hosted, and made part of
> gcc.gnu.org.

Feel free to set up a list on gcc.gnu.org; I do not have the access to
do that.  I felt that as a short-lived list, the precise hosting
location did not much matter.

zw

      parent reply	other threads:[~2003-06-09 23:01 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
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 [this message]

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=87fzmiua86.fsf@egil.codesourcery.com \
    --to=zack@codesourcery.com \
    --cc=ac131313@redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@sources.redhat.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).