Updating top-level autoconf to 2.59
Doug Evans
dje@transmeta.com
Fri Dec 8 22:12:00 GMT 2006
fwiw, I wouldn't mind an explanation for why
+m4_pattern_allow([AS_FOR_TARGET])dnl
is necessary. I've ran into that too. Blech.
Bonus points for adding a comment to the file to document the reason.
Steve Ellcey writes:
> All of the subtrees in the GCC and Src trees have been updated to use
> autoconf 2.59 and now that GCC 4.2 has branched I think it is time to
> update the toplevel configure script to use 2.59 too. I came up with
> the attached patch but I found that when I set (and exported) CC and
> then ran the GCC configure & make my build of libstdc++ failed because
> the build of the libstdc++ library was using my original bootstrap CC
> (the one used to build the new compiler) instead of the newly built g++
> like it does now. Does this problem sound familiar to anyone? Does
> anyone know how to fix it?
>
> If I set CC on the configure command line (instead of setting an
> environment variable before calling configure) it appeared to work but I
> don't think that that is what should be happening.
>
> Steve Ellcey
> sje@cup.hp.com
>
> Here is the patch I was trying:
>
>
> Index: configure.in
> ===================================================================
> --- configure.in (revision 119559)
> +++ configure.in (working copy)
> @@ -21,10 +21,12 @@
> sinclude(config/acx.m4)
>
> AC_INIT(move-if-change)
> -AC_PREREQ(2.13)
> +AC_PREREQ(2.59)
> AC_CANONICAL_SYSTEM
> AC_ARG_PROGRAM
>
> +m4_pattern_allow([AS_FOR_TARGET])dnl
> +
> # Get 'install' or 'install-sh' and its variants.
> AC_PROG_INSTALL
> ACX_PROG_LN
More information about the Binutils
mailing list