Correct automake and autoconf version requirements #701
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nicowilliams
added a commit
that referenced
this pull request
Feb 18, 2015
Correct automake and autoconf version requirements
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've tried to compile jq from the GitHub sources on Scientific Linux 6.6 and encountered a problem with generating the ./configure script using
autoreconf -i. As it turns out, the m4_esyscmd_s and AM_PROG_AR macros used in configure.ac are not available for autoconf 2.63 and automake 1.11.1 - the most recent versions for this particular distro release (and also for CentOS 6.6 and probably other RHEL 6.6 distributions, too) . However, compiling from the source tarball available from the jq download page works fine.The missing AM_PROG_AR gets added in automake 1.11.2 and m4_esyscmd_s gets added in autoconf 2.64. I'm sending you a pull request that reflects these requirements in the configure.ac file.