From: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
To: "Kaveh R. GHAZI" <ghazi@caip.rutgers.edu>
Cc: gcc-patches@gcc.gnu.org, binutils@sourceware.org, gdb@sourceware.org
Subject: Re: mini-freeze of autotools-governed files in GCC and src
Date: Sun, 23 Aug 2009 14:22:00 -0000 [thread overview]
Message-ID: <20090823140401.GA13304@gmx.de> (raw)
In-Reply-To: <Pine.GSO.4.58.0908230928220.10196@caipclassic.rutgers.edu>
* Kaveh R. GHAZI wrote on Sun, Aug 23, 2009 at 03:31:00PM CEST:
> On Sat, 22 Aug 2009, Ralf Wildenhues wrote:
>
> > The trees have been updated to Autoconf 2.64 and Automake 1.11. Please
> > take a minute to ensure that you use these tools now when changing build
> > system generated files;
>
> Why request developers ensure this and not bump the AC_PREREQ to make
> sure?
Toplevel config/override.m4 should already cause failure if you use
anything other than Autoconf 2.64 (but it doesn't ensure Automake 1.11).
However, if override.m4 isn't included in some directory (because that
hasn't been done yet, or because somebody ran aclocal with missing -I
arguments), then the test isn't used. So it's debatable whether
AC_PREREQ would help for that case. Since we pretty much require
override.m4 to fix a bug in 2.64, however, that doesn't really gain us
all that much. Better to just ensure it is used everywhere.
A few followup patches to binutils ensure Automake 1.11 there. I can
write one to ensure it in GCC as well (or think about a way to do it in
override.m4) if that is desired.
Cheers,
Ralf
next prev parent reply other threads:[~2009-08-23 14:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-22 15:45 Ralf Wildenhues
2009-08-22 19:10 ` NightStrike
2009-08-22 19:13 ` Ralf Wildenhues
2009-08-23 14:04 ` Kaveh R. GHAZI
2009-08-23 14:22 ` Ralf Wildenhues [this message]
2009-08-23 15:48 ` Kaveh R. Ghazi
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=20090823140401.GA13304@gmx.de \
--to=ralf.wildenhues@gmx.de \
--cc=binutils@sourceware.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=ghazi@caip.rutgers.edu \
/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