m4_map_args_w([a b c], [pre(], [)post], [
])[]text
expands to:
pre([a])post
pre([b])post
pre([c])post[]text
while without the newline,
m4_map_args_w([a b c], [pre(], [)post])[]text
expands to:
pre([a])post[]pre([b])post[]pre([c])post[]text
So far, so good,
==========================================================
results in this error:
==========================================================
$ make -f Makefile.devel check-configures AUTOCONF='autoconf --trace=CL_CLISP
--trace=_CL_CLISP_REQUIRE_FEATURE_2'
Ouch. Running autoconf --trace is meant to be independent of regenerating your
makefiles; it does NOT generate a configure file, but rather tells you about
what is happening under the hood. You need to run your normal:
$ make -f Makefile.devel check-configures
without any --trace lines added to AUTOCONF to see how the generated configures
behave (I see later in your email that you did this), and if you need the
traces, just run this in isolation:
$ autoconf path/to/configure.ac --trace=CL_CLISP --
trace=_CL_CLISP_REQUIRE_FEATURE_2
to see where those two macros are used within path/to/configure.ac (but without
generating any configure scripts).
Use of uninitialized value $macro in concatenation (.) or string at
/usr/bin/automake line 4831, <GEN0> line 40.
automake: ####################
automake: ## Internal Error ##
automake: ####################
automake: unrequested trace `'
Probably fallout from not creating actual configure files, due to the confusion
of when to use --trace.