Bug#1079874: valgrind: FTBFS with mpich instead of openmpi

user debian-rele...@lists.debian.org usertags 1079874 + bsp-2025-04-brazil thanks On Tuesday, December 17 2024, Graham Inggs wrote: > On Tue, 17 Dec 2024 at 08:25, Emanuele Rocca wrote: >> It seems that valgrind is currently building fine on both armhf and i386 >> with mpi-defaults 1.17: >> >> h

Bug#1079874: valgrind: FTBFS with mpich instead of openmpi

Hi Emanuele On Tue, 17 Dec 2024 at 08:25, Emanuele Rocca wrote: > It seems that valgrind is currently building fine on both armhf and i386 > with mpi-defaults 1.17: > > https://people.debian.org/~ema/valgrind_armhf-2024-12-17T09:07:39Z.build > https://people.debian.org/~ema/valgrind_i386-2024-12-

Processed: Re: Bug#1079874: valgrind: FTBFS with mpich instead of openmpi

Processing control commands: > tag -1 unreproducible Bug #1079874 [src:valgrind] valgrind: FTBFS with mpich instead of openmpi Added tag(s) unreproducible. -- 1079874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079874 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1079874: valgrind: FTBFS with mpich instead of openmpi

Control: tag -1 unreproducible Hi Graham, On 2024-08-28 11:19, Graham Inggs wrote: > Since the upload of mpi-defaults 1.17, switching the default MPI on > 32-bit architectures, valgrind FTBFS It seems that valgrind is currently building fine on both armhf and i386 with mpi-defaults 1.17: https:

Bug#1079874: valgrind: FTBFS with mpich instead of openmpi

Source: valgrind Version: 1:3.20.0-2.1 Severity: serious Tags: ftbfs Hi Maintainer Since the upload of mpi-defaults 1.17, switching the default MPI on 32-bit architectures, valgrind FTBFS [1][2]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://tests.