Hi On Fri, 24 Apr 2026 14:58:06, Drew Parsons <[email protected]> wrote: > The mumps build failure is in the nonofficial arches > hppa and powerpc, so broken support for them can't be considered > a RC bug. Hence reducing the severity of this bug to normal.
I don't think this bug is related to build failures on non-release architectures. I compared some of the libgmm-dev binary packages and found the following difference: $ diffoscope libgmm-dev_5.5+dfsg1-1_amd64.deb libgmm-dev_5.5+dfsg1-1_s390x.deb │ │ ├── ./usr/include/gmm/gmm_arch_config.h │ │ │ @@ -25,11 +25,11 @@ │ │ │ /* defined if superlu header files are not under a subdirectory called "superlu" */ │ │ │ /* #undef GMM_NO_SUPERLU_INCLUDE_SUBDIR */ │ │ │ │ │ │ /* Use blas with 64 bits integers */ │ │ │ /* #undef GMM_USE_BLAS64_INTERFACE */ │ │ │ │ │ │ /* defined if the BLAS fortran ABI does not return complex values directly (e.g. Intel's MKL) */ │ │ │ -/* #undef GMM_BLAS_RETURN_COMPLEX_AS_ARGUMENT */ │ │ │ +#define GMM_BLAS_RETURN_COMPLEX_AS_ARGUMENT /**/ │ │ │ │ │ │ /* GMM version */ │ │ │ #define GMM_VERSION "5.5" One solution is to simply drop the Multi-Arch: same field from the libgmm-dev binary package (only). See a similar bug reported against libtrilinos-kokkos-kernels-dev [1]. Regards Graham [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1133738
