From: Paolo Bonzini <bonzini@gnu.org>
To: Benjamin Kosnik <bkoz@redhat.com>
Cc: ralf.wildenhues@gmx.de, gcc@gcc.gnu.org
Subject: Re: updating autotools status
Date: Wed, 15 Jul 2009 06:25:00 -0000 [thread overview]
Message-ID: <4A5D764E.5040306@gnu.org> (raw)
In-Reply-To: <20090714121746.3a6c46e7@mcgee.artheist.org>
On 07/14/2009 09:17 PM, Benjamin Kosnik wrote:
> Hey Ralf! Saw your message about updating gcc/src to current auto
> tools, in favor. But, it looks like the autoconf 2.64 release is not
> out, last I see is 2.63b at the end of March. This and
> confirmation of --with-build-sysroot working seem to be the only open
> issues standing in the way of the conversion of the GCC source
> repository.
>
> What's the eta for the 2.64 autoconf release? How is this to be timed
> with the end of GCC Stage 1? If autoconf 2.64 is not out by the end of
> July, does it make sense to use autoconf 2.63 instead?
Once we switch to 2.60 or later, we can always require the latest and
greatest just like we did between 2.54 and 2.59.
Paolo
next prev parent reply other threads:[~2009-07-15 6:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-14 19:18 Benjamin Kosnik
2009-07-15 6:25 ` Paolo Bonzini [this message]
2009-07-21 6:41 ` Ralf Wildenhues
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=4A5D764E.5040306@gnu.org \
--to=bonzini@gnu.org \
--cc=bkoz@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=ralf.wildenhues@gmx.de \
/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).