Bug#1050503: suitesparse: FTBFS on loong64 and sparc64 due to packaging issues

John Paul Adrian Glaubitz <[email protected]>
Newsgroups gmane.linux.debian.ports.sparc
Message-ID <169296683578.844660.13072165562850665466.reportbug__41839.3089597643$1692967000$gmane$org@nofan.physik.fu-berlin.de>
Source: suitesparse
Version: 1:7.1.0+dfsg-3
Severity: normal
User: [email protected]
Usertags: sparc64
X-Debbugs-Cc: [email protected]

Hello!

suitesparse FTBFS on loong64 and sparc64 due a packaging issue with an implicit CUDA
dependency. The failing build step is actually at dpkg-shlibdeps which fails since it
cannot find the lib*_cuda.so shared libraries anywhere [1][2]:

 dpkg-shlibdeps: error: cannot find library libspqr_cuda.so.3 needed by debian/libspqr3/usr/ \
 lib/sparc64-linux-gnu/libspqr.so.3.0.4 (ELF format: 'elf64-sparc' abi: '0202002b00000000'; RPATH: '')
 dpkg-shlibdeps: error: cannot find library libcholmod_cuda.so.4 needed by debian/libumfpack6/ \
 usr/lib/sparc64-linux-gnu/libumfpack.so.6.1.1 (ELF format: 'elf64-sparc' abi: '0202002b00000000'; RPATH: '')
 dpkg-shlibdeps: error: cannot find library libcholmod_cuda.so.4 needed by debian/libklu2/usr/ \
 lib/sparc64-linux-gnu/libklu_cholmod.so.2.0.4 (ELF format: 'elf64-sparc' abi: '0202002b00000000'; RPATH: '')

This is not surprising since the corresponding lib*_cuda.so shared libraries are being
deleted in debian/rules [3]. However, I have no clue why this affects loong64 and sparc64
only.

Adrian

> [1] https://buildd.debian.org/status/fetch.php?pkg=suitesparse&arch=loong64&ver=1%3A7.1.0%2Bdfsg-3&stamp=1692910284&raw=0
> [2] https://buildd.debian.org/status/fetch.php?pkg=suitesparse&arch=sparc64&ver=1%3A7.1.0%2Bdfsg-3&stamp=1692414038&raw=0
> [3] https://salsa.debian.org/science-team/suitesparse/-/blob/master/debian/rules#L57

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.