Add CI for Windows MinGW (using MSYS2) #85
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Author
|
The error with LLVM Flang looks similar to the compilation error with the Intel Fortran compiler that is described here: For that project, it apparently helped to remove a |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds CI for building FlexiBLAS for Windows MinGW using the compiler toolchain and packages from MSYS2. Overall it is very similar to the existing CI that is running on Ubuntu images.
MSYS2 is a collection of tools and libraries providing you with an easy-to-use environment for building, installing and running native Windows software. It provides toolchains and packages for different build environments. These build environments mainly differ in the compiler toolchains (GCC vs. LLVM) that are used, the C/C++ libraries, and the target architecture (i686, x86_64, or arm64).
I chose to use the UCRT64, the CLANG64, and the CLANGARM64 environments. Please, let me know if you prefer to test with more or other environments.
The only environment that is currently capable of building for Windows on ARM is one that is based on LLVM (CLANGARM64). The Fortran compiler of that toolchain is LLVM Flang.
While this Fortran compiler has already come a long way in supporting most features that
gfortransupports (and partly more), it is (still) incompatible/incomplete in some aspects (unfortunately).It looks like there are some build issues with LLVM Flang. I'm not sure how to address them. Maybe, you'll have an idea how to interpret the error messages.
That's why the CI for the CLANG64 and CLANGARM64 environments is failing.
MSYS2 is cherry-picking a few patches from upstream when building the reference BLAS/LAPACK implementations:
https://github.com/msys2/MINGW-packages/blob/fc18ee4334b70d1daa411525209ea4d9d81cb295/mingw-w64-lapack/PKGBUILD#L30-L32
Maybe, they are also needed in the vendored version of LAPACK? (They don't really look related to the build errors to me.)
Independently, the test suite is failing in the UCRT64 environment. That environment is based on a GCC toolchain. It uses the "Universal C Runtime" (UCRT) as the Windows C library. The UCRT is a more modern implementation of the C library (compared to the older MSVCRT).
Like you wrote in #76 (comment), those test errors are likely due to how
xerblais implemented in shared libraries (if I understood correctly).