-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OpenBLAS version number in binaries #4
Comments
This only applies to the file names themselves--we can always know for sure with the usual ctypes calls through get_config(). Still, it can cause confusion. |
This was referenced Jun 3, 2019
Merged
This will be closed when we move entirely to the wheels |
We have moved to wheels. Closing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The binaries that are generated from this repo can, in some cases, have OpenBLAS version numbers that are not a reflection of what has actually been built.
Usually in these cases the correct commit hash on the OpenBLAS development branch will be included in the file name despite the incorrect OpenBLAS version specification.
This probably shouldn't happen--especially since we now have programmatic access to a version string directly from openblas get_config(). It causes confusion for reviewers & communication with OpenBLAS team.
The text was updated successfully, but these errors were encountered: