-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Ralf Wildenhues on 3/24/2008 7:03 AM: | Good idea. It is just a wee bit ugly that branch-1_4 ends with an | unusable release. OK, you've convinced me (or else I must be in a conceding mood this morning) - I'm releasing M4 1.4.11 this week, with only a single behavioral patch above and beyond 1.4.10 (ie., no speedups from argv_ref, just the fopen(name,"a+") bug fix). Any preferences on whether M4 or autoconf should come first? | I'm fine with that, too, postponing everything that might still be open. | What I'd like to do until then is get the AM_COND_IF mess sorted out | (so that lib/autom4te.cfg is in shape for the next Automake) and | investige the Autoconf build failure I saw on MinGW with M4-1.4.10. | | Just to be sure, "this weekend" is the March 29 one, right? Yes, unless you need more time on the AM_COND_IF stuff. I'll try looking into the MinGW failure, but I'm not sure how long it will take me to reproduce it (I don't normally build in MinGW; rather, I tend to cross-compile with cygwin as host and mingw as target). |> I'm installing this to the M4 NEWS file. Should I also push a patch to |> the autoconf repository branched off of 2.59, to provide a gitweb URL to |> the minimal patch to lib/m4sugar/m4sugar.m4 which is required to get 2.59 |> to build with newer M4? | | Good idea. That will come later today. I guess I'll have to tag it to make it easy to find from gitweb. - -- 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 iEYEARECAAYFAkfnqD8ACgkQ84KuGfSFAYA4lgCeITxXUxL3ognHrs3VASLHQ8J6 1KAAoKKmgHKTvqWav6tHS7qgh9WDxIXK =WGMf -----END PGP SIGNATURE----- _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
