Remove obsolete AC_GECODE_TIMER M4 macro from configure.ac.in #197
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
In bc31c31 Gecode's timer handling was unified to std::chrono::steady_clock. This removed the need for checking at build time for which timer to use and AC_GECODE_TIMER M4 macro was removed that tested for them but the configure.ac.in still had the call, breaking autotools build.
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.
In bc31c31 Gecode's timer handling was unified to std::chrono::steady_clock. This removed the need for checking at build time for which timer to use and AC_GECODE_TIMER M4 macro was removed that tested for them but the configure.ac.in still had the call, breaking autotools build.