Fix lapack support check in CPU/OpenCL backend CMakeLists #3027
Conversation
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.
Description
Prior to this change, if the build environment doesn't have non-MKL LAPACK libraries installed while Intel MKL is installed, then even when the user didn't turn ON using MKL due to the current check, LAPACK was enabled which resulted in build failure with missing headers/libraries.
Changes to Users
None to Application developers unless they are building ArrayFire themselves. In which case, they would now be able to build ArrayFire without linear algebra routines support in the above specified scenario.
Checklist
[ ] Functions added to unified API[ ] Functions documented