On 11/12/2012 03:13 PM, Nick Bowler wrote: >> If libtool will get the information in a different way, then that new >> way must return the same information - and that implies that autoconf >> now has to do something with AC_CONFIG_MACRO_DIR. > > On this point, I disagree: the way to maintain compatibility is to not > change this macro, and instead add a totally new one (which we've done: > it's called AC_CONFIG_MACRO_DIRS with an S) that new packages can make > use of if they want, and old packages can continue to not use. > > I thought my examples already demonstrated where the proposed changes > would cause existing, *working* configure.ac files to fail after > updating to a version of Autoconf with the changes.
Our point is that any configure.ac with two or more AC_CONFIG_MACRO_DIR is NOT working. It was merely lucky that it wasn't tripping over other problems. But since we can't make it continue to work with the new semantics of AC_CONFIG_MACRO_DIRS, the best we can do (and indeed, what we DID do) is loudly flag incorrect usage as an error rather than silently change semantics. > The backwards-compatible way of handing AC_CONFIG_MACRO_DIR is to have > it do exactly what it has done for the past 10 years: nothing useful. When used exactly once, it does just that. -- Eric Blake [email protected] +1-919-301-3266 Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
