Hi, On Wed, May 23, 2012 at 2:17 AM, Bob Friesenhahn <bfriesen@xxxxxxxxxxxxxxxxxxx> wrote: > The forthcoming Automake release is about to break the means I have been > using to automatically version my package (without manually editing > configure.ac) for the past 9 years. I am told to use m4 code in the AC_INIT > arguments in order to supply package versioning information. This is what I > am using: > > AC_INIT(m4_esyscmd([scripts/pkginfo.sh package_name]), > m4_esyscmd([scripts/pkginfo.sh package_version]), > m4_esyscmd([scripts/pkginfo.sh package_bugreport])) > > Unfortunately, this approach works exactly once since Autoconf 2.69 is > caching the computed arguments passed to AC_INIT. Running 'autoconf' or > 'autoreconf' again does not result in an updated configure script. Running > 'autoconf --force' in the source tree seems to work. Thanks for bringing this up. I noticed this problem also some weeks ago, but we still use autoconf 2.68 and automake 1.11.1. I couldn't follow it lately, but the last thing I know was that you can disable the caching via a file named '.autom4te.cfg' besides your configure.ac with the following content: begin-language: "Autoconf" args: --no-cache end-language: "Autoconf" Bert > > Bob _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx https://lists.gnu.org/mailman/listinfo/autoconf
