-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
autoreconf -fi fails with 'autoreconf: automake failed with exit status: 1' #4
Comments
Thanks for the report. I'll check it out. |
Hmm. Just tried this now, on Raspbian Stretch Lite (4.9.44+ August 2017)
Seemed to be okay. |
This happens when libtoolize tries to be smart about the auxiliary files directory: if there is a pi@raspberrypi:~/alac $ touch ../install.sh
pi@raspberrypi:~/alac $ autoreconf -fi
aclocal: warning: couldn't open directory 'm4': No such file or directory
libtoolize: putting auxiliary files in '..'.
libtoolize: copying file '../ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:40: installing './compile'
configure.ac:63: installing './config.guess'
configure.ac:63: installing './config.sub'
configure.ac:20: installing './install-sh'
configure.ac:63: error: required file './ltmain.sh' not found
configure.ac:20: installing './missing'
Makefile.am: installing './INSTALL'
codec/Makefile.am: installing './depcomp'
autoreconf: automake failed with exit status: 1
pi@raspberrypi:~/alac $ A quick and dirty workaround is to install alac from a directory where there is no @mikebrady I have no idea about libtoolize, is there a way to avoid this behaviour? |
Thanks for the post, but I am not getting the same behaviour:
This is on a fully up-to-date Raspberry Pi 4. -- Version 10.9, "Buster".
|
Did you try to create (an empty) |
Apologies, I misread your post. You're right -- putting that I'm afraid I don't have a fix for it. |
No problem – it already helps a lot to know that it should be installed in a directory that does not have an |
On Raspbian Stretch, installation fails on first run:
The offending line being
libtoolize: putting auxiliary files in '..'.
- so it tries to putltmain.sh
a directory up from where it's supposed to be.On running autoreconf a second time (when m4 already exists), it appears to put the files in the correct location, and configure appears to work as intended
The text was updated successfully, but these errors were encountered: