Skip to content
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

GA 5.6 release - autotools are downloaded and built even when latest versions exist #33

Closed
ajaypanyala opened this issue Apr 11, 2017 · 6 comments
Assignees

Comments

@ajaypanyala
Copy link
Member

When trying to build GA-5.6 release tarball - autoconf2.69, automake 1.11 and libtool 2.4.6 are downloaded and built even when these versions exist.

@abhinavvishnu
Copy link
Contributor

Hi Jeff:

Ajay recently pointed out to this. Can you please take care of it?

Thanks,

:- Abhinav

@jeffhammond
Copy link
Member

I know I am not the Jeff you meant, but I will try to work on this as well. Given how many places I use that script, I have a selfish interest in making it as efficient as possible 😉

@jeffhammond jeffhammond self-assigned this Apr 14, 2017
@jeffdaily
Copy link
Member

Something else to check in the script -- I just heard from a colleague that the script fails to download the various tarballs due to port restrictions. They're able to git clone the repo just fine, but wget fails. I also tried, but the problem is that the FTP port is blocked. I'm not sure how to resolve this unless there is another URL for downloading the tarballs.

@ajaypanyala
Copy link
Member Author

M4_VERSION_MIN is set to 1.4.12. When the script finds m4 say v1.4.13 on the system, it proceeds to download and install autoconf-2.69, but the autoconf configure script fails with the error

checking for GNU M4 that supports accurate traces... configure: error: no acceptable m4 could be found in $PATH.
GNU M4 1.4.6 or later is required; 1.4.16 or newer is recommended.
GNU M4 1.4.15 uses a buggy replacement strstr on some systems.
Glibc 2.9 - 2.12 and GNU M4 1.4.11 - 1.4.15 have another strstr bug.
FAILURE 3

I set M4_VERSION_MIN=1.4.16 to avoid this error (M4-1.4.17 gets downloaded and built)

@jeffdaily
Copy link
Member

I've tried to fix this in the hotfix/5.6.1 branch. I hope it's working better now.

@ajaypanyala
Copy link
Member Author

It works now. Thanks Jeff!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants