-
Notifications
You must be signed in to change notification settings - Fork 67
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
Linking error on Windows 11 using Intel MKL as static library #310
Comments
As a follow-up, this seems possibly consistent with LTO bugs in rustc itself: rust-lang/rust#51009 |
I'm not able to reproduce this error on Arch Linux with
That warning before the error message is strange:
Do you have any ideas regarding that message? Do you still get an error if you run |
Apologies for missing your reply! I did still get the issue on Windows 11 even when running |
Rerunning at the command-line with rust-analyzer disabled, I reproduce the above on Windows 11:
The error persists after running
Running in a fresh Docker container from the
|
I'm not sure I'll be able to help much with this; my time is pretty limited, and I don't have a Windows machine set up for Rust development. Some suggestions:
|
I see this issue on Windows Server but not on my windows 10 and windows 11 machine. I cant figure out why it does not work on the Windows server machine. |
When compiling a small crate against
ndarray-linalg
using theintel-mkl-static
feature, linking errors result depending on the value oflib.crate-type
inCargo.toml
.Example crate
Example error:
Running
cargo build
works for some settings oflib.crate-type
, however:["rlib", "staticlib", "cdylib"]
: fails["staticlib", "cdylib"]
: works["rlib", "staticlib"]
: works["rlib"]
: works["staticlib"]
: works["rlib", "cdylib"]
: fails["cdylib"]
: worksVersion info
The text was updated successfully, but these errors were encountered: