Hi,
I am writing on behalf of my team from Endava company. Our task is to work with
opensource community, and setup multiple applications for use on win11 arm64
machines.
One of the tasks is to understand the problems and if possible help NumPy team
in setting up win11 arm64 compatible wheel on
We will start looking at the bug and the CI job.
Thanks,
Slobodan
___
NumPy-Discussion mailing list -- numpy-discussion@python.org
To unsubscribe send an email to numpy-discussion-le...@python.org
https://mail.python.org/mailman3/lists/numpy-discussion.
As the bug fix is merged we are starting the investigation on the CI job.
I have a few questions about this:
1) Are there some additional instructions for making and running the numpy CI
jobs and cross compilation available in the documentation?
2) Do we need to have arm64 scipy-openblas released
Hi,
I finished the first step and created the workflow for cross-compiling wheel
without OpenBlas. PR for this can be found at:
https://github.com/numpy/numpy/pull/27330
Output wheel is successfully installed and tested on the arm machine.
After this gets merged I will continue with adding the
Hi,
I made the second PR for full wheel with openblas. It is reviewed, but solution
with openblas is not good enough, so I am investigating alternate options for
cross compiling openblas.
While I am working on this I have one question about the wheel without
OpenBLAS. As the job is now created
Sorry for misunderstanding. I accidentally created this thread from Windows 11
arm64 wheel. That is also the reason why there is no subject. I will repost
this to that discussion.
It was not strictly openblas problem. I was trying to make the gh actions build
for win11 arm64 numpy with openbla
I accidentally created new thread without subject with message that is
belonging here:
Hi,
I made the second PR for full wheel with openblas. It is reviewed, but rejected
as solution with linaro built openblas is not good enough, so I am
investigating alternate options for cross compiling openb
