On 6/2/24 14:51, Collin Funk wrote:
I don't know enough about Autotools to tell if anything silly can be
done using this trick. Not that you would run auto* in a project that
you don't trust anyways...
Right, but the glitch is worth documenting. I installed the attached
into Autoconf.From 3a7aa01e2ada483c5790dc9ea1d761fd75248ff2 Mon Sep 17 00:00:00 2001
From: Paul Eggert <egg...@cs.ucla.edu>
Date: Fri, 5 Jul 2024 20:32:40 +0100
Subject: [PATCH] doc: mention ACLOCAL_AMFLAGS and #
* doc/autoconf.texi: Mention that ACLOCAL_AMFLAGS
cannot use makefile comments. Problem reported by
Collin Funk in:
https://lists.gnu.org/r/bug-gnulib/2024-06/msg00005.html
---
doc/autoconf.texi | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/doc/autoconf.texi b/doc/autoconf.texi
index cb148398..ee3f2f7a 100644
--- a/doc/autoconf.texi
+++ b/doc/autoconf.texi
@@ -1821,7 +1821,8 @@ If you want @command{autoreconf} to pass flags that are not listed here
on to @command{aclocal}, set @code{ACLOCAL_AMFLAGS} in your @file{Makefile.am}.
Due to a limitation in the Autoconf implementation these flags currently
must be set on a single line in @file{Makefile.am}, without any
-backslash-newlines. Also, be aware that future Automake releases might
+backslash-newlines or makefile comments.
+Also, be aware that future Automake releases might
start flagging @code{ACLOCAL_AMFLAGS} as obsolescent, or even remove
support for it.
@@ -2171,7 +2172,7 @@ Note that if you use @command{aclocal} from an Automake release prior to
in your top-level @file{Makefile.am}. Due to a limitation in
the Autoconf implementation of @command{autoreconf}, these include
directives currently must be set on a single line in @file{Makefile.am},
-without any backslash-newlines.
+without any backslash-newlines or makefile comments.
@end defmac
@prindex @command{config.guess}
--
2.45.2
