WindowsArm64 coverage

[giorgosHadji]

Hello, didn't manage to find anything so asking here.

Does lapack support windows arm64?

I have seen and successfully build openBLAS but can't see anything for LAPACK.

Also I read that openBLAS should include LAPACK on its own, so I am kinda confused if it actually does or not.

The next step on my development which is currently failing and hence I am here is that my cmake can't seem to find LAPACK, although finds openBLAS (compiling kaldi on win ARM64)

[martin-frbg]

The current LAPACK builds fine with the WoA version of LLVM19, I just checked this a few hours ago.

OpenBLAS does contain a copy of the Reference LAPACK as well (with only a few functions overridden by reimplementations), but its latest release does not yet have all updates from 3.12.1 (notably the build system changes to enable both the normal and "INTERFACE64" long-integer array index versions of functions in the same build of the library are missing).

Which version of CMake, and how are you making it look for LAPACK, find_package(LAPACK) or something else ?

[giorgosHadji]

Thanks for the immediate response.
Cmake versions: 3.31.4
yes I use find_package(LAPACK REQUIRED)

FYI specifically I get:

[cmake] -- Found BLAS: /opt/lib/openblas.lib
[cmake] CMake Error at kaldi/cmake/FindLAPACK.cmake:477 (message):
[cmake]   A required library with LAPACK API not found.  Please specify library
[cmake]   location.

[martin-frbg]

If this is with OpenBLAS only, you might be running into https://gitlab.kitware.com/cmake/cmake/-/issues/24874

[giorgosHadji]

I tried with both on/off and both have the same result.

Anyway I can verify my openblas is actually with LAPACK support?

I did compiled it with the correct flag, but doesnt hurt eliminating things.

Any other suggestions I can try to debug further?

If lapack is with openblas, is it in a different library or directory? not sure how exactly they are packaged together or what

[martin-frbg]

same library; use dumpbin or similar to check if LAPACK symbol names are present in the library, also see if cmake created any error/log files that might have details on where it was searching. but this is going off-topic here...