-
Notifications
You must be signed in to change notification settings - Fork 6.2k
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] Upgrade to 0.3.21 and add arm64-windows support #26396
Conversation
Thanks for submitting this PR, I got an error when I tested
Log from
|
@FrankXie05 Are you using Visual Studio 17.3 Preview 3 or later? Because it only works with it. |
@nursik Sorry, the version I tested is |
I tested with the latest VS version, but the result is still the same error. :(
And the version of Log from
install-arm64-windows-dbg-out.log |
Can you send me your Visual Studio's configuration file? |
There is a configuration file for 17.3 preview 5 for x64 host. BTW the build process was successful on x64 and ARM64 machines. |
@nursik Sorry for the late reply, here is the configuration file I exported for my |
@FrankXie05 I was trying to figure out why you cannot build it, while my machine and CI/CD could do that. And only now I figured out that you trying to install openblas[*], not only core :) I tried openblas[core,simplethread,threads] on x64 and it works. For dynamic-arch feature I need to check a possible regression from 0.3.20. |
@FrankXie05 I tested various combinations of features, and you can see the results below. Could you please confirm that ARM machinearm64-windows triplet
x64-windows triplet
x86_64 machinearm64-windows triplet
x64-windows triplet
|
@nursik Thank you for your test results, based on the latest test results of CI, I chose to approve this PR, maybe there is something wrong with my local |
@@ -201,6 +201,7 @@ discord-rpc:x64-uwp=fail | |||
# requires g++11 | |||
discordcoreapi:x64-linux=fail | |||
dlib:arm-uwp=fail | |||
dlib:arm64-windows=fail |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it ok that some ports are marked as fail instead of being fixed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
By fixing you mean adding !(arm & windows)
to vcpkg.json files or fixing the ports' build processes?
@@ -234,6 +235,7 @@ embree2:arm64-osx=skip | |||
embree2:arm64-osx=skip | |||
epsilon:arm-uwp=fail | |||
epsilon:x64-uwp=fail | |||
faiss:arm64-windows=fail |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you explain why these ports are being marked as fail?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These ports are dependent on OpenBLAS and did not implicitly support arm64-windows. Because OpenBLAS was not supported for arm64-windows, these ports were failing to be installed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@JavierMatosD Are you suggesting changing vcpkg.json files, instead of removing these packages from baseline
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, I think this is fine :)
Change label for JavierMatosD review. |
Thank you! |
What does your PR fix?
Upgrades to 0.3.21 and adds
arm64-windows
triplet.arm-uwp
removedWhich triplets are supported/not supported? Have you updated the CI baseline?
!(arm & uwp), Yes
Does your PR follow the maintainer guide?
Yes
If you have added/updated a port: Have you run
./vcpkg x-add-version --all
and committed the result?Yes