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 Ralf Wildenhues on 3/23/2008 5:44 PM:
| Hello Eric,
|
| I think an inadvertent backward incompatibility has been introduced.

It was intentional - POSIX requires m4wrap to have FIFO behavior:
http://git.sv.gnu.org/gitweb/?p=m4.git;a=commitdiff;h=ca0ae27

| I'm pretty sure this problem is rather recent.

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

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.

- --
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

iEYEARECAAYFAkfm89IACgkQ84KuGfSFAYDedwCfRA8+nmsWyef9IuOeJHbZO8gQ
NlAAoKsG1JHpwtGgHgpiIqn+BrlaGcT1
=NY89
-----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