On 01/18/2013 01:33 PM, Diego Elio Pettenò wrote: > On 18/01/2013 13:28, Stefano Lattarini wrote: >> >> While removing those macros seemed quite harmless, because it didn't >> put a real burden on the developers (requiring them just to do a quick >> edit to configure.ac), it turned out to place an unsustainable burden >> on distro packagers who use the latest Automake to bootstrap existing >> packages. Many of them still used AM_CONFIG_HEADER, and the removal >> of this macro would have forced the packages to patch all those. > > FWIW at least on my side, AM_CONFIG_HEADER is not that much of a big > deal. It's a simple sed (which we could reasonably apply as a global > hack, just not really keen on using said hacks), and the functionality > transpose directly. > > AM_PROG_CC_STDC is a different story so I'd be glad to get that one back. > > Also for the record, in Gentoo 1.13.1 turns out to be mild in comparison > to 1.12 or 1.11 — right now we only have four bugs, and only one still > open (which I can fix this afternoon): > > https://bugs.gentoo.org/show_bug.cgi?id=automake-1.13 > > While I'm by far not complete with running the tests on our packages, > usually I get much more trouble much faster. > I'm glad to now the situation isn't as bleak as I feared. Still, the Fedora packagers have already decided to patch their Automake 1.13.1 to reinstate the AM_CONFIG_HEADER and AM_PROG_CC_STDC macros (plus other macros that I don't believe it's worth worrying about though):
<http://www.spinics.net/lists/fedora-devel/msg176098.html> <http://pkgs.fedoraproject.org/cgit/automake.git/commit/?id=ffe6bc39> So, rather than having one more incompatibility floating around, I'd rather mirror that change (or its relevant part) in mainstream. Thanks, Stefano