At least when installed by spack, we've observed SuperLU 5.3.0 to generate some invalid strings in its {prefix}/lib/pkgconfig/superlu.pc. The libdir value is set to the prefix appended to the libdir. like this:
libdir=/home/wspear/bin/SPACK/spack/opt/spack/linux-ubuntu22.04-westmere/gcc-11.3.0/superlu-5.3.0-e4dr3j4nfn6ry2mikrprlfn5ukgpb4in//home/wspear/bin/SPACK/spack/opt/spack/linux-ubuntu22.04-westmere/gcc-11.3.0/superlu-5.3.0-e4dr3j4nfn6ry2mikrprlfn5ukgpb4in/lib
Which isn't an actual path.
And when configured with intel-mkl the Libs.private value appends all of the paths and libraries together in a semicolon separated blob which pkg-config exports as-is and is not valid compiler input.
At least when installed by spack, we've observed SuperLU 5.3.0 to generate some invalid strings in its {prefix}/lib/pkgconfig/superlu.pc. The libdir value is set to the prefix appended to the libdir. like this:
libdir=/home/wspear/bin/SPACK/spack/opt/spack/linux-ubuntu22.04-westmere/gcc-11.3.0/superlu-5.3.0-e4dr3j4nfn6ry2mikrprlfn5ukgpb4in//home/wspear/bin/SPACK/spack/opt/spack/linux-ubuntu22.04-westmere/gcc-11.3.0/superlu-5.3.0-e4dr3j4nfn6ry2mikrprlfn5ukgpb4in/libWhich isn't an actual path.
And when configured with intel-mkl the Libs.private value appends all of the paths and libraries together in a semicolon separated blob which pkg-config exports as-is and is not valid compiler input.