config.status: error: cannot find input file: `Makefile.in'

[ghost]

Hey,

I keep getting this error: "config.status: error: cannot find input file: `Makefile.in'" while performing "./configure". Any ideas?

I am using the latest commit (19th April 2012), Ubuntu 11.10. Tried to get PAM headers like the instructions said by installing "libpam0g-dev". Was that sufficient? Please let me know if I should be providing more information.

Thanks,
James

[jeroennijhof]

Hey James,

Seems there went something wrong with your autotools.

Please do the following in the root of the source:
aclocal
autoconf
autoheader
automake --add-missing

There should be no error messages or whatever, after that you should be
able to run configure.

With kind regards,
Jeroen Nijhof

On 05/17/2012 03:32 PM, jamesfu wrote:

Hey,

I keep getting this error: "config.status: error: cannot find input file: `Makefile.in'" while performing "./configure". Any ideas?

I am using the latest commit (19th April 2012), Ubuntu 11.10. Tried to get PAM headers like the instructions said by installing "libpam0g-dev". Was that sufficient? Please let me know if I should be providing more information.

Thanks,
James

---

Reply to this email directly or view it on GitHub:
#1

[ghost]

Hey Jeroen,

Thanks for your help! Finally got it to install correctly (I think). Not sure what fixed the problem for me, as I tried a number of things like the PAM headers and "autoreconf" and didn't checkout a clean copy of the package and restart from aclocal, autoconf... after each action.

I'd like to share my experience here, in the hopes it'd benefit someone else and if found note-worthy, merged into the INSTALL and README files (I'm running Ubuntu 11.10, packaging tool commands will vary for other flavours):

1. Download personalization tool for Linux:
   http://www.yubico.com/personalization-tool
2. Uncompress and run with elevated privileges or YubiKey will not be detected
3. Follow instructions in Section 5.2.1 of the user guide to reprogram YubiKey, noting the AES Key (Samir from Yubico has confirmed they no longer reveal factory programmed AES Keys for security reasons):
   http://static.yubico.com/var/uploads/pdfs/Cross_Platform_YubiKey_Personalization_Tool_3.0.1_User_guide_v4.pdf
4. This command installs the autotools and PAM headers needed for yubipam to compile (they were not pre-installed for me)
   sudo apt-get install autoconf automake libtool libpam0g-dev

EDIT
4.1. Run "libtoolize" prior to "aclocal" or "automake --add-missing" may complain of "configure.ac:28: required file `config/ltmain.sh' not found"

1. Follow instructions in INSTALL, running with elevated privileges from step 4 (sudo make install) onwards
2. In step 7 I found "yk_chkpwd" to be in a different location so I did this instead:
   sudo chgrp yubiauth /etc/yubikey /usr/local/sbin/yk_chkpwd
3. And again in step 9:
   sudo chmod g+s /usr/local/sbin/yk_chkpwd
4. In step 10, the file I updated was:
   /etc/pam.d/common-auth
5. The rest of the steps for managing users are well-documented in README, just remember to run ykpasswd & ykvalidate with elevated privileges

Now, I've run into a different set of issues with ykvalidate. I'll start a new issue on that and hope I can start using my new YubiKey for logins soon!

Cheers,
James

[jeroennijhof]

Hi James,

Nice it's working for you now.
I have some small remarks for you below:

On 05/18/2012 12:42 PM, jamesfu wrote:

Hey Jeroen,

Thanks for your help! Finally got it to install correctly (I think). Not sure what fixed the problem for me, as I tried a number of things like the PAM headers and "autoreconf" and didn't checkout a clean copy of the package and restart from aclocal, autoconf... after each action.

I'd like to share my experience here, in the hopes it'd benefit someone else and if found note-worthy, merged into the INSTALL and README files (I'm running Ubuntu 11.10, packaging tool commands will vary for other flavours):

1. Download personalization tool for Linux:
   http://www.yubico.com/personalization-tool
   If you are using Ubuntu you can simply do apt-get install
   yubikey-personalization
2. Uncompress and run with elevated privileges or YubiKey will not be detected
3. Follow instructions in Section 5.2.1 of the user guide to reprogram YubiKey, noting the AES Key (Samir from Yubico has confirmed they no longer reveal factory programmed AES Keys for security reasons):
   http://static.yubico.com/var/uploads/pdfs/Cross_Platform_YubiKey_Personalization_Tool_3.0.1_User_guide_v4.pdf
4. This command installs the autotools and PAM headers needed for yubipam to compile (they were not pre-installed for me)
   sudo apt-get install autoconf automake libtool libpam0g-dev
5. Follow instructions in INSTALL, running with elevated privileges from step 4 (sudo make install) onwards
6. In step 7 I found "yk_chkpwd" to be in a different location so I did this instead:
   sudo chgrp yubiauth /etc/yubikey /usr/local/sbin/yk_chkpwd
7. And again in step 9:
   sudo chmod g+s /usr/local/sbin/yk_chkpwd
8. In step 10, the file I updated was:
   /etc/pam.d/common-auth
9. The rest of the steps for managing users are well-documented in README, just remember to run ykpasswd & ykvalidate with elevated privileges
   The whole point of having a helping binary yk_chkpwd with setgid is that
   you can run ykvalidate without elevated privileges. ykvalidate will
   execute yk_chkpwd to check if the OTP is correct.

With kind regards,
Jeroen

[ghost]

Hey Jeroen,

You're right, as always, about ykvalidate. However, does ykpasswd use yk_chkpwd? When I run it without elevated privileges, I get: "Unable to access the database: /etc/yubikey [2]"

Cheers,
James

[jeroennijhof]

Hi James,

No, ykpasswd doesn't use yk_chkpwd and should be run with elevated
privileges indeed.

Ykvalidate and the PAM module itself are using yk_chkpwd to validate the
OTP.

Regards,
Jeroen

On 05/20/2012 05:04 AM, jamesfu wrote:

Hey Jeroen,

You're right, as always, about ykvalidate. However, does ykpasswd use yk_chkpwd? When I run it without elevated privileges, I get: "Unable to access the database: /etc/yubikey [2]"

Cheers,
James

---

Reply to this email directly or view it on GitHub:
#1 (comment)

[hsanjuan]

I will comment that I had the same Makefile.in problem mentioned in this issue. I had to run autoreconf. Im on OpenSUSE 12.1... it seems that the autoconf tools are not behaving the same way. I have version 2.68.

[hxpax]

Got the same error on Ubuntu 1404 with autoreconf.

[OnnoKampman]

Got the same error, fixed it as follows.

It turned out I had a folder in the path to the openSMILE folder with a space in the folder name. './configure' couldn't deal with that. After removing the white space it executed.

[shivammutreja]

Anybody here while installing secp256k1. Follow this answer - https://stackoverflow.com/a/22625555/4631231

[malikabid]

.in'ig.status: error: cannot find input file: `Makefile