FlexiBLAS provides incorrect pc files

[Micket]

Currently, our flexiblas installations provide

flexiblas.pc  flexiblas_api.pc  lapack.pc  lapacke.pc

where in particular

$ cat /apps/Test/software/FlexiBLAS/3.4.5-GCC-14.3.0/lib/pkgconfig/lapack.pc 
libdir=/apps/Test/software/FlexiBLAS/3.4.5-GCC-14.3.0/lib
includedir=/apps/Test/software/FlexiBLAS/3.4.5-GCC-14.3.0/include/flexiblas

Name: LAPACK
Description: FORTRAN reference implementation of LAPACK Linear Algebra PACKage
Version: 3.12.0
URL: http://www.netlib.org/lapack/
Libs: -L${libdir} -llapack
Requires.private: blas

makes no sense. This file should either not exist at all (since there is no "liblapack.so", and there is no "blas.pc" either).
Even just attempting to use it it broken

pkg-config --libs lapack
Package blas was not found in the pkg-config search path.
Perhaps you should add the directory containing `blas.pc'

This file should either just be removed, or perhaps a better choice is to make both blas.pc and lapack.pc just be symlinks to flexiblas.pc.

---

Secondly, the lapacke.pc

$ cat /apps/Test/software/FlexiBLAS/3.4.5-GCC-14.3.0/lib/pkgconfig/lapacke.pc 
libdir=/apps/Test/software/FlexiBLAS/3.4.5-GCC-14.3.0/lib
includedir=/apps/Test/software/FlexiBLAS/3.4.5-GCC-14.3.0/include/flexiblas

Name: LAPACKE
Description: C Standard Interface to LAPACK Linear Algebra PACKage
Version: 3.12.0
URL: http://www.netlib.org/lapack/#_standard_c_language_apis_for_lapack
Libs: -L${libdir} -llapacke
Cflags: -I${includedir}
Requires.private: lapack

is again just indirectly broken as it points to lapack(.pc) which is broken by itself. so. I suppose this would just be fixed it we did the symlink above, or we should change it to Requires.private: flexiblas.

[Micket]

Hm. To add to this, lapacke.so that we build with FlexiBLAS needs suffixed xxxx_64_ ILP64 type symbols, which FlexiBLAS just does not provide at all.
There is no libflexiblas64.so either.

So, liblapacke that we provide here is completely useless.

[Thyre]

Both of these .pc files are created by the reference LAPACK. See:

• https://github.com/Reference-LAPACK/lapack/blob/66380df1cacbcb62d4bfbc4b603cf0925aa7492c/LAPACKE/lapacke.pc.in
• https://github.com/Reference-LAPACK/lapack/blob/66380df1cacbcb62d4bfbc4b603cf0925aa7492c/lapack.pc.in

The broken thing here is that lapack.pc is always generated, even if we did not build LAPACK. LAPACKE also always expects that lapack.pc exists. So their build system is broken.

I agree that going the symlink route is probably a good idea to work around this...