This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Do not use autoconf 2.60 yet
- From: "Joseph S. Myers" <joseph at codesourcery dot com>
- To: echristo at gcc dot gnu dot org, echristo at apple dot com
- Cc: gcc at gcc dot gnu dot org
- Date: Tue, 14 Nov 2006 16:20:18 +0000 (UTC)
- Subject: Do not use autoconf 2.60 yet
- References: <20061109235658.19704.qmail@sourceware.org>
On Thu, 9 Nov 2006, echristo@gcc.gnu.org wrote:
> Author: echristo
> Date: Thu Nov 9 23:56:57 2006
> New Revision: 118633
>
> URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=118633
> Log:
> 2006-11-09 Eric Christopher <echristo@apple.com>
>
> PR bootstrap/26892
> PR bootstrap/27814
> PR other/28994
> * configure.ac: Match powerpc*-*-darwin* for powerpc darwin checks.
> * config.gcc (powerpc64-*-darwin*): New target.
> * config.host: Ditto.
> * config/rs6000/darwin64.h: New file.
> * config/rs6000/x-darwin64: Ditto.
> * config/rs6000/host-ppc64-darwin.c: Ditto.
You appear to have regenerated configure, on both mainline and 4.2 branch,
with autoconf 2.60. Could you please regenerate it with 2.59 in both
places? 2.59, exactly, is the version documented in install.texi. In
order to avoid random churn with versions going back and forth and
different versions in different directories with no good reason, we must
have a transition plan before changing the version used (and keep
install.texi up to date throughout the transition with what version is
used in what directory), and we have no such plan; certainly such changes
are inappropriate on release branches. The changes to directory variables
and new configure options in autoconf 2.60 make such a transition plan
especially important (for example, we need to work out at what point the
local configure options --with-datarootdir --with-docdir --with-htmldir
get removed in each directory in favour of the standard options added in
2.60). 2.60 also needs automake 1.10 (and vice versa).
--
Joseph S. Myers
joseph@codesourcery.com