configure is designed so that it appears to do everything
itself, but there is actually a hidden slave: config.status.
configure is in charge of examining your system, but it is
config.status that actually takes the proper actions based on
the results of configure. The most typical task of config.status
is to instantiate files. This section describes the common
behavior of the four standard AC_CONFIG_LINKS. They all have
this prototype: AC_CONFIG_ITEMS(tag..., [commands], [init-cmds])
where the arguments are: You are encouraged to use literals as
tags. In particular, you should avoid ... && my_foos="$my_foos
fooo" ... && my_foos="$my_foos foooo"
AC_CONFIG_ITEMS([$my_foos]) and use this instead: ... &&
AC_CONFIG_ITEMS([fooo]) ... && AC_CONFIG_ITEMS([foooo]) special
tag values: they may have the form ‘output’ or ‘output:inputs’.
The file output is instantiated from its templates, inputs
(defaulting to ‘output.in’).
‘AC_CONFIG_FILES([Makefile:boiler/top.mk:boiler/bot.mk])’, for
example, asks for the creation of