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
autogen.sh fails when only automake needs to be built #49
Comments
This is my suggested patch |
This makes we wonder if we just shouldn't unconditionally force all of them to build...? |
Yes, it might be a good idea just to force to build all of them to avoid this kind of troubles. |
I have just realized that the autogen.sh script seems to fail even when all the four autotools components are present with the required versions (log attached). Therefore, the best option might just be to build all of them unconditionally as you suggested. |
Just pushed eecc838 to try and fix this. Please try again and report back. Thanks. |
Yes, that commit fixes the case when all the four autotools components are present |
The autogen.sh fails to build the right set of autotools when only automake needs to be built, while m4, libtool and autoconf are already at the required version. I think that the script fails since the automake build has a hardwired reference to ../autotools/share/aclocal that should come from libtool, but libtool has not been built. A simple solution would be to build libtool even though it has the required version already.
Here are some snippets from the attached log file
+ M4_VERSION=1.4.17
+ LIBTOOL_VERSION=2.4.6
+ AUTOCONF_VERSION=2.69
../ga-5-6-1/autotools/share/aclocal': No such file or directory
autogen.log.txt
The text was updated successfully, but these errors were encountered: