Check to see if we need to link against CoCoA when detecting libnormaliz (autotools) #3464
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
Use it for the e-antic check
Previously, we always linked against nauty, but it might not be necessary if libnormaliz was built w/o the nauty package
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.
On Fedora, the autotools check for libnormaliz was failing because the Fedora normaliz package is built with CoCoA support. We add a check, similar to the existing one for e-antic, to see if we need to add
-lcocoato the build flags when detecting it.We introduce a macro,
CHECK_NMZ_PACKAGE, to simplify this process and also use it to check if libnormaliz was built with nauty support.