Re: branch-1_4 cannot build Autoconf 2.59 any more

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Eric Blake on 3/23/2008 6:20 PM:
| Rather, Autoconf 2.59 was relying on an M4 bug, which has since been
| patched in autoconf:
| http://git.sv.gnu.org/gitweb/?p=autoconf.git;a=commitdiff;h=814d1a1

The more relevant patch is:
http://git.sv.gnu.org/gitweb/?p=autoconf.git;a=commitdiff;h=66931ce

|
| However, the m4 patch mentioned above also mentions a way to restore the
| older m4 behavior, in examples/wraplifo.m4.  Modulo quoting differences,
| this could be used to guarantee correct autoconf 2.59 behavior on those
| projects that are not yet ready to upgrade.

So, for example, you could submit a patch to gcc to add this to
configure.ac (or one of the files it includes), prior to calling AC_INIT:

# As long as we aren't ready to upgrade to autoconf 2.60,
# make sure that newer M4 will still use LIFO order:
m4_define([arg1], [$1])dnl
m4_define([m4_wrap],
[m4_if([_$0_text],
~  [m4_define([_$0_text], [$1]m4_defn([_$0_text]))],
~  [m4_builtin([m4wrap],
~    [arg1(m4_defn([_$0_text])m4_undefine([_$0_text]))])dnl
m4_define([_$0_text], [$1])])])dnl

- --
Don't work too hard, make some time for fun as well!

Eric Blake             ebb9@xxxxxxx
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkfm+hkACgkQ84KuGfSFAYBZcACgscwBQntrSU/OSxYdja4RDOvc
NgAAn1FhUyC7uLZZFjySEaBn26rk1SMB
=fKfH
-----END PGP SIGNATURE-----


_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf

[Index of Archives]     [GCC Help]     [Kernel Discussion]     [RPM Discussion]     [Red Hat Development]     [Yosemite News]     [Linux USB]     [Samba]

  Powered by Linux