Source: valgrind Version: 1:3.24.0-3 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: debian-...@lists.debian.org, debian-powe...@lists.debian.org, mp...@packages.debian.org User: debian-...@lists.debian.org Usertags: armhf User: debian...@lists.debian.org Usertags: i386 User: debian-powe...@lists.debian.org Usertags: powerpc
While checking why the fix for #1057621 wasn't migrating to testing, I noticed that the updated valgrind has failed to build on armhf and i386, as well as the -ports architecture powerpc. (This means that it built successfully on every 64-bit architecture that it supports, but failed to build on every 32-bit architecture.) The build failure: > dh_install -pvalgrind -Xlibmpiwrap > dh_install --remaining-packages > dh_install: warning: Cannot find (any matches for) > "usr/lib/*/valgrind/libmpiwrap*" (tried in ., debian/tmp) > > dh_install: warning: valgrind-mpi missing files: > usr/lib/*/valgrind/libmpiwrap* > dh_install: error: missing files, aborting 1:3.24.0-2 built successfully, but it seems unlikely for this to have been triggered by the only change in 1:3.24.0-3, which was the fix for #1057621, <https://salsa.debian.org/debian/valgrind/-/commit/2528eb684823b991035092bd27bd4ff354d22914> which seems to be unrelated to the error message. Instead I think this must have been triggered by a change in some other package - perhaps mpich, which is the MPI implementation used on 32-bit? - between 2025-01-22 and 2025-04-13. I see that valgrind's configure check for mpi-c is failing: > checking for mpicc... /usr/bin/mpicc > checking for pkg-config... /usr/bin/pkg-config > checking pkg-config is at least version 0.9.0... yes > checking for mpi-c... no > gcc: error: unrecognized command-line option '-showme:compile' > gcc: error: unrecognized command-line option '-showme:link' > checking primary target for usable MPI2-compliant C compiler and mpi.h... no This might be related to the mpich and mpi-defaults autopkgtest regressions seen with the version in unstable, #1102928 and #1089694. If this is really a mpich regression, the bug can be reassigned to mpich with an "affects" on src:valgrind. Thanks, smcv
