On 18 March 2011 21:06, Reuben Thomas <r...@sc3d.org> wrote: > On 18 March 2011 21:03, Eric Blake <ebl...@redhat.com> wrote: >> On 03/18/2011 02:58 PM, Reuben Thomas wrote: >>> On 18 March 2011 20:56, Eric Blake <ebl...@redhat.com> wrote: >>>> On 03/18/2011 02:53 PM, Reuben Thomas wrote: >>>>> Just now doing a git merge I caught sight of an AC_PREREQ line in one >>>>> .m4 file. Is there a built-in way to extract the required versions of >>>>> autoconf, automake &c. from an autotools build system? (I can't find >>>>> an answer, but there's an awful lot of cool undocumented stuff in >>>>> there at present.) >>>> >>>> autoconf --trace AC_PREREQ >>>> >>>> and look through that for the largest number. >> >> As a note of caution, note that just inspecting trace output might not >> tell you the whole story. If you use automake 1.11, you will get an >> AC_PREREQ of autoconf 2.62 from AM_INIT_AUTOMAKE. But gnulib can be >> used with anything as old as autoconf 2.59, provided you are also using >> an older automake to go with it (and once you do switch to an older >> automake, you will no longer see the AC_PREREQ 2.62 in the trace). > > That was timely, I made exactly that mistake, and since there was > quite a gap between 2.61 & 2.62, I guess it's worth fixing the minimum > in my INSTALL file. Thanks!
Gary Vaughan points out that in fact "Autoconf-2.61[...]is prior to bug-fixes relied on by the warnings and manywarnings gnulib modules". This doesn't show up with the AC_PREREQ test; am I missing something? (He demonstrates this by getting errors when trying to bootstrap a build system using those modules with autoconf 2.61.) -- http://rrt.sc3d.org
