configure: remove or replace obsolete macros#3199
Closed
nilason wants to merge 1 commit intoOSGeo:mainfrom
Closed
Conversation
This eliminates warnings running autoconf with version 2.71. Note: the file 'configure' is still created by and fully compatible with version 2.69. One issue involving <time.h> vs. <sys/time.h> remains and now issues a separate warning. Solving that includes changes in code and must be addressed separately.
Contributor
Author
|
I reckon this will not be needed as #2281 is on the line. |
This file contains hidden or 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 eliminates warnings running autoconf with version 2.71. Note: the file 'configure' is still created by and fully compatible with version 2.69. This does not represent a change to generate the configure file by 2.71, but that change will eventually be merely formal.
One issue involving <time.h> vs. <sys/time.h> remains and now issues a separate warning. Solving that includes changes in code and must be addressed separately.
The changes of this PR is in practice a subset of #2281, without the official move to 2.71.