Unresolved symbols if INDEX64_EXT_API_DEFAULT enabled

[Enimalojd]

Building on ALT Workstation K 11.1 (Nemorosa) there was a problem when trying to update the package version. In our distribution, after the package is built, the verify-elf check is started.
After commit ce3f662, the build broke with an error:

verify-elf: ERROR: ./usr/lib64/liblapack.so.3.12.0: undefined symbol: cdotc_64_
verify-elf: ERROR: ./usr/lib64/liblapack.so.3.12.0: undefined symbol: zherk_64_
verify-elf: ERROR: ./usr/lib64/liblapack.so.3.12.0: undefined symbol: ctpmv_64_
verify-elf: ERROR: ./usr/lib64/liblapack.so.3.12.0: undefined symbol: sgemv_64_
verify-elf: ERROR: ./usr/lib64/liblapack.so.3.12.0: undefined symbol: strsm_64_
verify-elf: ERROR: ./usr/lib64/liblapack.so.3.12.0: undefined symbol: cdotu_64_
verify-elf: ERROR: ./usr/lib64/liblapack.so.3.12.0: undefined symbol: cgbmv_64_
verify-elf: ERROR: ./usr/lib64/liblapack.so.3.12.0: undefined symbol: ssbmv_64_
verify-elf: ERROR: ./usr/lib64/liblapack.so.3.12.0: undefined symbol: zher2_64_
verify-elf: ERROR: ./usr/lib64/liblapack.so.3.12.0: undefined symbol: zgerc_64_
verify-elf: ERROR: ./usr/lib64/liblapack.so.3.12.0: undefined symbol: ctpsv_64_
verify-elf: ERROR: ./usr/lib64/liblapack.so.3.12.0: undefined symbol: dgemv_64_
verify-elf: ERROR: ./usr/lib64/liblapack.so.3.12.0: undefined symbol: dtbsv_64_
verify-elf: ERROR: ./usr/lib64/liblapack.so.3.12.0: undefined symbol: ztrmm_64_
verify-elf: ERROR: ./usr/lib64/liblapack.so.3.12.0: undefined symbol: ztbsv_64_
verify-elf: ERROR: ./usr/lib64/liblapack.so.3.12.0: undefined symbol: cherk_64_
verify-elf: ERROR: ./usr/lib64/liblapack.so.3.12.0: undefined symbol: zaxpy_64_

[martin-frbg]

these are BLAS symbols which should be present in libblas.so.3.12.0 - can you please check (ideally with a separate tool like nm) if they are there or not ?

[Enimalojd]

[builder@localhost ~]$ nm -D /usr/lib64/libopenblas.so | grep "zgerc_"
0000000000145910 T zgerc_

[martin-frbg]

Looks like you're setting up your build of Reference-LAPACK to use an external BLAS rather than the unoptimized Reference BLAS that is included ? OpenBLAS has not yet switched to providing both 32 and 64bit-integer versions of all functions in the same library, so you'll need to make sure that your copy of OpenBLAS was built with INTERFACE64=1 if you want to use it with INDEX64_EXT_API_DEFAULT