# all files in this directory included in the distribution
DIST = ChangeLog COPYRIGHT DATE INSTALL MACHINES README VERSION \
ChangeLog install-sh mkinstalldirs Makefile.in aclocal.m4 \
- acconfig.h config.h.in configure.in configure stamp-h.in \
+ acconfig.h config.h.in configure.ac configure stamp-h.in \
config.sub config.guess
# subdirectories in distribution
config.status: configure VERSION
./config.status --recheck
-configure: configure.in aclocal.m4
+configure: configure.ac aclocal.m4
cd $(srcdir) && autoconf
config.h: stamp-h
./config.status config.h stamp
config.h.in: stamp-h.in
-stamp-h.in: configure.in acconfig.h aclocal.m4
+stamp-h.in: configure.ac acconfig.h aclocal.m4
cd $(srcdir) && autoheader
date > $@
dnl If this macro accepted a list of include,library tuples
dnl to test in order that would be cleaner than the current
-dnl nest of calls in configure.in.
+dnl nest of calls in configure.ac.
dnl We try to link our own code fragment (which includes the
dnl headers in the same way slocal.c does) rather than
dnl
-dnl configure.in -- autoconf template for nmh
+dnl configure.ac -- autoconf template for nmh
dnl
dnl Move this up a bit
a minimum of autoconf 2.54.
Most of the configure-related files are automatically generated. The only files
-you should need to manually edit are acconfig.h and configure.in. Don't, for
+you should need to manually edit are acconfig.h and configure.ac. Don't, for
instance, edit config.h.in. Though it is an input file from the point of view
of the users (and the configure script) it is an output file from the point of
view of the developers (and the autoconf script).