On 07/01/2018 10:13 PM, John Calcote wrote:
On Sun, Jul 1, 2018, 2:54 PM Sascha Manns <Sascha.Manns@xxxxxxxxxx> wrote:
[ 22s] checking that generated files are newer than configure... done
[ 22s] configure: creating ./config.status [ 22s] config.status: error:
cannot find input file: ` .in'
Is that space literally part of the error message? Or is email garbling
the spacing?
This error is coming from the AC_CONFIG_FILES line. You seem to be
specifying both the input and output files for some of the entries but not
for all of them. You may do this but your syntax is incorrect.
Start by removing all of the lines in the macro argument that end in .in.
Well, most of them. But po/Makefile.in is actually a typical
AC_CONFIG_FILES target, as gettext ships a po/Makefile.in.in (yes, with
the double suffix), and does it's own thing later on during make to
convert po/Makefile.in into an actual Makefile without having to depend
on automake (although typically you don't store either po/Makefile.in.in
nor po/Makefile.in in version control, as they are generated files).
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
https://lists.gnu.org/mailman/listinfo/autoconf
