-
Notifications
You must be signed in to change notification settings - Fork 77
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
Not able to compile on intel based Mac #315
Comments
Fwiw, I can reproduce this (Intel CPU, macOS 10.15, rustc 1.60.0). Changing |
maybe related to https://github.com/blas-lapack-rs/openblas-src#20 , as they appear to have been post-processing the generated Makefile.conf to eliminate the libgfortran reference ? (that would work for pure BLAS builds as it is"only" LAPACK that is written in Fortran) Upcoming OpenBLAS 0.3.21 will include copies of the LAPACK sources converted to C |
Hello all, It seems with OpenBLAS 0.3.21, similar error appears when statically linking (dynamic linking is ok) for my intel MacOS (Monterey): = note: Undefined symbols for architecture x86_64: I tried both to use CC from brew installed gcc and also llvm clang (also brew installed), put /usr/local/bin/CC and /usr/local/bin/cc to link to the brew installed gcc or clang. Neither works. Hope there is a work around for static link, which is quite useful for me. Thanks, Jianshu |
when doing static linking, you will need to link in libgfortran.a - or build OpenBLAS-0.3.21 with the NOFORTRAN option to get f2c-translated versions of the LAPACK functions instead of the original Fortran ones. |
Hello, How exactly can I do that? Since i use v 0.15 from crate.io. Thanks Jianshu |
This is intel-mkl-static static link error (dynamic link is ok) on intel MacOS: = note: Undefined symbols for architecture x86_64: error: could not compile Any idea? Thanks, Jianshu |
running example with static is ok. The above mentioned error appeared when link to a binary statically for other binary crates. Jianshu |
Issue I have
Code to reproduce this issue
cargo.toml
just do
cargo run
will reproduce this issueVersion information
Any help/pointer will be appreciated!
The text was updated successfully, but these errors were encountered: