-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
[LAPACK] build failure #20323
Comments
Please attach the failure log first. Thanks. |
We don't have enough information to solve this issue, unfortunately; if you have any more information to help us solve this, please reopen! |
Hello @JackBoosY, I have a similar error and thought it might be better to comment instead of opening a whole new issue. Here are the logs config-x64-windows-out.log:
CmakeError.log:
CmakeOutput.log:
|
@lukadriel7 Confirmed. |
Under windows, you can temporarily use clapack instead of lapack-reference to solve this problem.
|
This issue should be fixed by #21479. |
This problem affects too many ports. I think it may need to be repaired as soon as possible. |
Sorry to ask here. I have same problem with 2024.7.10 vcpkg:
If I build my project directly, everything is fine. But when I build it with
Could please help with it, or give me some debug suggestion? |
@dg0yt Any suggestions here? |
related problem #41048 |
Host Environment
To Reproduce
Steps to reproduce the behavior:
`./vcpkg install lapack:x64-windows
Failure logs
Please ensure you're using the latest portfiles with
.\vcpkg update
, thensubmit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: lapack:x64-windows
Vcpkg version: 2021-05-05-9f849c4c43e50d1b16186ae76681c27b0c1be9d9
Additionally, attach any relevant sections from the log files above.
Additional context
This error occured when I tried to vcpkg ceres solver, then I remove all package and tried to only vcpkg lapack, it occured again.
this log I can't understand well, thank you for your help!
The text was updated successfully, but these errors were encountered: