Re: config.status: error: cannot find input file: ` .in'
On Mon, Jul 2, 2018 at 3:27 PM Eric Blake wrote: > On 07/01/2018 10:13 PM, John Calcote wrote: > > On Sun, Jul 1, 2018, 2:54 PM Sascha Manns > 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@gnu.org https://lists.gnu.org/mailman/listinfo/autoconf
Re: config.status: error: cannot find input file: ` .in'
On 07/01/2018 10:13 PM, John Calcote wrote: On Sun, Jul 1, 2018, 2:54 PM Sascha Manns 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@gnu.org https://lists.gnu.org/mailman/listinfo/autoconf
Re: config.status: error: cannot find input file: ` .in'
On Sun, Jul 1, 2018, 2:54 PM Sascha Manns 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' > 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. The macro will infer the input file from the specified output file. John > ___ Autoconf mailing list Autoconf@gnu.org https://lists.gnu.org/mailman/listinfo/autoconf
Re: config.status: error: cannot find input file: `po/Makefile.in.in'
On Sun, May 19, 2013 at 9:57 AM, Kip Warner k...@thevertigo.com wrote: Hey list, I have my message catalogues in a directory in my project other than in the usual po/. I ran gettextize --po-dir=folder. I also updated Makevars's subdir to point to the new directory. The SUBDIRS variable in my Makefile.am also points to the right location. However, the error I am receiving when I run ./configure is the following, despite po/ not existing: config.status: error: cannot find input file: `po/Makefile.in.in' Any help appreciated. Do you still have a reference to po in configure.ac? Sections 13.4 and 13.4.5 in the gettext manual look relevant to your problem. ___ Autoconf mailing list Autoconf@gnu.org https://lists.gnu.org/mailman/listinfo/autoconf
Re: config.status: error: cannot find input file: `po/Makefile.in.in'
On Sun, 2013-05-19 at 10:38 +0100, Gavin Smith wrote: Do you still have a reference to po in configure.ac? Sections 13.4 and 13.4.5 in the gettext manual look relevant to your problem. Hey Gavin. I already went through the manual, but I'm guessing I must have missed something. Indeed, I had. I just found the problem was in a side effect gettextize left in configure.ac in AC_CONFIG_FILES which pointed to the dead po/. I missed that the first time I went through it, but thanks for bringing that to my attention. But back to the manual, I see there's a lot of things that need to be modified all over the place in an autotooled project to use gettext, but one thing I wasn't sure of was how much of it still needs to be done manually after gettextize has managed to gettext'ify the project? -- Kip Warner -- Software Engineer OpenPGP encrypted/signed mail preferred http://www.thevertigo.com signature.asc Description: This is a digitally signed message part ___ Autoconf mailing list Autoconf@gnu.org https://lists.gnu.org/mailman/listinfo/autoconf
