Discussion:
config.status: error: cannot find input file: ` .in'
Sascha Manns
2018-07-01 19:31:49 UTC
Permalink
Hello List,

on [1] i prepared a program.
On [2] i provided a config.ac.
Now i’m executing ./autogen.sh and i’m getting:

[ 21s] checking for python3 script directory...
${prefix}/lib/python3.4/site-packages
[ 21s] checking for python3 extension module directory...
${exec_prefix}/lib64/python3.4/site-packages
[ 22s] checking that generated files are newer than configure... done
[ 22s] configure: creating ./config.status [ 22s] config.status: error:
cannot find input file: ` .in'
[ 22s] error: Bad exit status from /var/tmp/rpm-tmp.PomKe1 (%build)

But i don’t find any error in the config.ac. Maybe i missed anything?

Greetings
Sascha

[1] https://github.com/saigkill/ignore-me
[2] https://github.com/saigkill/ignore-me/blob/develop/configure.ac


Sincerly yours

Sascha Manns
Maifeldstraße 10
56727 Mayen
Phone: +49-2651-4014045
Mobile: +49-172-3142738
Web: https://saigkills-backtrace.de
GPG-Crypto-Key: B069886BF34BD3D1ED200B8C4AB3235A21AF27AC
X.509-Zertifikat: https://saigkills-backtrace.de/***@outlookde.crt
John Calcote
2018-07-02 03:13:17 UTC
Permalink
Post by Sascha Manns
[ 22s] checking that generated files are newer than configure... done
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
Eric Blake
2018-07-02 21:27:47 UTC
Permalink
This post might be inappropriate. Click to display it.
John Calcote
2018-07-03 16:25:11 UTC
Permalink
Post by Eric Blake
Post by John Calcote
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

Loading...