Le mercredi 12 juillet 2023 à 16:05 +0200, Andreas Tille a écrit : > Am Wed, Jul 12, 2023 at 03:34:09PM +0200 schrieb Rafael Laboissière: > > When generating the C++ code, the xmds tool tries to link against > > libcblas.so, which, currently, only exists in the libatlas-base-dev package. > > I admit this is actually the reason why any of the packages I'm maintaining > depends from libatlas-base-dev: These are linking against libcblas which is > only provided in this package. If we might find a way to provide some kind > of "wrapper" so other implementations could provide libcblas as well, this > could be some generic solution. Unfortunately I'm probably pretty naive > and I'm asking for the impossible. Short version: any package that links against libcblas can normally be fixed by linking against libblas. Long version: for historical reasons, libblas.so in Debian contains both the BLAS Fortran routines, and a C interface to these routines (called CBLAS). Hence all the symbols that are in libcblas.so (which have the common “cblas_” prefix) are present in libblas.so. (Note that this is different from the LAPACK case: liblapack.so only includes the Fortran routines, while the C interface is provided by the separate liblapacke.so). You can check this for yourself by running the following commands: $ objdump -T /usr/lib/x86_64-linux-gnu/libblas.so $ objdump -T /usr/lib/x86_64-linux-gnu/libcblas.so -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name ⠈⠳⣄⠀⠀⠀⠀ https://www.debian.org
Attachment:
signature.asc
Description: This is a digitally signed message part