On Mon, Jul 2, 2018 at 3:27 PM Eric Blake <eblake@xxxxxxxxxx> wrote: > On 07/01/2018 10:13 PM, John Calcote wrote: > > On Sun, Jul 1, 2018, 2:54 PM Sascha Manns <Sascha.Manns@xxxxxxxxxx> > wrote: > > > 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). > Wow - I wondered for a half second if it were possible the input files were named with .in.in extensions, but immediately discounted that possibility. I guess that'll teach me. John _______________________________________________ Autoconf mailing list Autoconf@xxxxxxx https://lists.gnu.org/mailman/listinfo/autoconf
