Re: AC_OUTPUT vs m4 nesting limit

[Andreas Schwab]

Akim Demaille <address@hidden> writes:

|> | Akim Demaille <address@hidden> writes:
|> | |> BTW, you might want to use several AC_CONFIG_FILES.  Using a single
|> | |> huge AC_OUTPUT seems bizarre to me.
|> | 
|> | That does not help, since AC_CONFIG_FILES just collects the files.  They
|> | are actually processed by AC_OUTPUT.
|> 
|> Hm... but IIRC there is no M4 loop to output the code in AC_OUTPUT.
|> ISTR it was implemented via a diversion.

It is part of _AC_OUTPUT_CONFIG_STATUS:

AC_FOREACH([AC_File], AC_LIST_FILES,
[  'm4_patsubst(AC_File, [:.*])' )dnl
 CONFIG_FILES="$CONFIG_FILES AC_File" ;;
])dnl

|> Actually, the limit you might be hitting might be due to the macro
|> which checks that there are no duplicates :(

This can be worked around, because it only loops on the list actually
passed to AC_CONFIG_FILES.

Andreas.

-- 
Andreas Schwab                                  "And now for something
SuSE Labs                                        completely different."
address@hidden
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5