build: fix unneeded workaround for AC_CONFIG_LINKS old bud

* configure.ac: The Automake NEWS entry for version 1.11 states that

    For AC_CONFIG_LINKS, if source and destination are equal, do
    not remove the file in a non-VPATH build.  Such setups work
    with Autoconf 2.62 or newer.

Since our build system requires autoconf >= 2.62 and automake >= 1.11
already, we can get rid of the workaround for that long-fixed bug.

Signed-off-by: Stefano Lattarini <stefano.lattarini@gmail.com>

diff --git a/configure.ac b/configure.ac
index c6291b3004aea5e0e140fce15e724ee9284a88a7..34522184d59eb776cdad2added028ab5e5ef7c91 100644 (file)
--- a/configure.ac
+++ b/configure.ac
@@ -205,13 +205,7 @@ AC_PROG_MAKE_CASE_SENSITIVE
 ## ------------ ##
 
 dnl Allow maintainer rules under GNU make even in VPATH builds.
-dnl Meanwhile, we must use a shell variable so that we bypass automake's
-dnl attempts to remove the sole copy of GNUmakefile in a non-VPATH build
-dnl during 'make distclean'.
-dnl TODO avoid the shell variable once automake is fixed.
-GNUmakefile=GNUmakefile
-AC_CONFIG_LINKS([$GNUmakefile:$GNUmakefile], [],
-                [GNUmakefile=$GNUmakefile])
+AC_CONFIG_LINKS([GNUmakefile:GNUmakefile])
 
 AC_CONFIG_FILES([Makefile doc/Makefile
                 lib/Makefile lib/Autom4te/Makefile lib/autoscan/Makefile