Public bug reported: mpi-defaults was recently changed to use mpich on 32-bit archs [1] (vis- a-vis openmpi on 64-bit).
Thanks to debian/patches/adjust_armhf_cases.patch, the valgrind configure scripts hard-code the MPI dependency on "mpi-c" which comes with openmpi only. This causes failures while building libmpiwrap* libraries which are part of the valgrind-mpi package. See build failure here [2]. ginggs has raised the same bug against Debian [3] [1] https://launchpad.net/ubuntu/+source/mpi-defaults/1.17 [2] https://launchpadlibrarian.net/743779270/buildlog_ubuntu-oracular-armhf.valgrind_1%3A3.23.0-0ubuntu1_BUILDING.txt.gz [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079874 ** Affects: valgrind (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse ** Description changed: mpi-defaults was recently changed to use mpich on 32-bit archs [1] (vis- a-vis openmpi on 64-bit). Thanks to debian/patches/adjust_armhf_cases.patch, the valgrind configure scripts hard-code the MPI dependency on "mpi-c" which comes with openmpi only. This causes failures while building libmpiwrap* libraries which are part of the valgrind-mpi package. See build failure here [2]. - ginggs has the same bug against Debian [3] + ginggs has raised the same bug against Debian [3] [1] https://launchpad.net/ubuntu/+source/mpi-defaults/1.17 [2] https://launchpadlibrarian.net/743779270/buildlog_ubuntu-oracular-armhf.valgrind_1%3A3.23.0-0ubuntu1_BUILDING.txt.gz [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079874 ** Tags added: update-excuse -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078264 Title: valgrind FTBFS on armhf (and i386) where mpi-defaults use mpich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/valgrind/+bug/2078264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
