* Ben Pfaff <[email protected]>, 2012-08-05, 13:02:
I wanted to use AC_CONFIG_HEADERS with multiple input files. I hoped
that autoheader will generate the first one for me. What it did
instead was to generate a file with a ":" in name:
| $ cat configure.ac
| AC_INIT([dummy])
| AC_CONFIG_HEADERS([config.h:config.h.in:config.aux.h])
| AC_OUTPUT
|
| $ ls -1 config.*
| config.aux.h
|
| $ autoheader
|
| $ autoconf
|
| $ ls -1 config.*
| config.aux.h
| config.h.in:config.aux.h
|
| $ ./configure
| configure: creating ./config.status
| config.status: error: cannot find input file: `config.h.in'
It looks like it was reported upstream years ago:
http://lists.gnu.org/archive/html/bug-autoconf/2007-06/msg00012.html
Can you use multiple calls to AC_CONFIG_HEADERS to solve your problem?
The autoconf manual says that AC_CONFIG_HEADERS may be called any
number of times, and that autoheader applies to the first invocation.
I've already worked around this by using AH_BOTTOM, so I don't need
_another_ work-around. :) I just want autoheader to do the right thing.
But no, if you have multiple AC_OUTPUT for the same output file, all you
get is:
$ autoconf
configure.ac:3: error: `config.h' is already registered with AC_CONFIG_HEADERS.
../../lib/autoconf/status.m4:713: AC_CONFIG_HEADERS is expanded from...
configure.ac:3: the top level
autom4te: /usr/bin/m4 failed with exit status: 1
--
Jakub Wilk
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
