> By the way, can I > AC_PREREQ(2.61a-341) Use AC_PREREQ([2.61a-341]), in case a (malicious) user does m4_define([a],[oops]) prior to using automake macros.
> now in order to be able to assume fixed AC_PROG_INSTALL? > I mean, it seems to be working, but I haven't checked with > Autoconf older than 2.59, and I don't know whether the version > comparison will get things right with the git version and all. Until my git changes, AC_PREREQ was pretty much unchanged from autoconf 2.58, and has been exiting with status 63 since 2003. And while older versions of autoconf are not as robust at version parsing, they don't need to parse the arbitrary suffix to correctly determine that they don't meet the prefix of 2.61, so you will get the desired version-mismatch error. Git autoconf will parse into the suffix, but since it handles suffix parsing correctly, that is not a problem either. So yes, you are safe bumping the AC_PREREQ now. -- Eric Blake -- View this message in context: http://www.nabble.com/AC_PROG_INSTALL%3A-require-installation-of-multiple-files.-tp15009115p15055899.html Sent from the Gnu - Automake - Patches mailing list archive at Nabble.com.
