-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
The static feature doesn't static link to the in-tree openblas on Debian Bullseye when libopenblas-dev is installed #60
Labels
Comments
Apparently Ubuntu Focal has the same issue:
|
maoe
added a commit
to maoe/openblas-src
that referenced
this issue
Mar 24, 2021
…hing else Fixes blas-lapack-rs#60. The gnu linker searches libraries in the order of -L options and stops the search when the first matching library is found. This means if libopenblas.a is either in deriv.make_conf.c_extra_libs.search_path or in deliv.make_conf.f_extra_libs.search_path, the in-tree libopenblas.a won't be used. This patch fixes the issue by printing the rustc-link-search instruction for the in-tree openblas before everything else.
maoe
added a commit
to maoe/openblas-src
that referenced
this issue
Mar 24, 2021
…hing else Fixes blas-lapack-rs#60. The gnu linker searches libraries in the order of -L options and stops the search when the first matching library is found. This means if libopenblas.a is either in deliv.make_conf.c_extra_libs.search_path or in deliv.make_conf.f_extra_libs.search_path, the in-tree libopenblas.a won't be used. This patch fixes the issue by printing the rustc-link-search instruction for the in-tree openblas before everything else.
Thanks a lot! |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
The static feature is (I think) supposed to build the openblas source in the submodule and link it statically but it appears that on Debian Bullseye it links to the system library (libopenblas-dev) instead. On Ubuntu Bionic it seems to work fine.
Steps to reproduce:
FWIW OpenBLAS 0.3.13 is installed via apt-get install in both containers.
The text was updated successfully, but these errors were encountered: