autoreconf fixes #939
Merged
autoreconf fixes #939
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
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.
This is for any fixes after the recent merges.
libnfs is failing when using the tarball from github, but not the tarball from sites.google.com. The tarball from sites.google.com is a repackaged version of the original git source code - it includes
configureandMakefile.in(which means autoreconf isn't required) yet these files aren't in git. So when building the tarball from git, the build now fails because autoreconf is disabled. Some files are also missing from the sites.google.com tarball (eg.arosfolder) - the existence of this google tarball is a bit of a mystery. Switching to github.com and restoring autoreconf is the easiest fix.