Your message dated Sun, 06 Apr 2025 15:46:16 -0400
with message-id <87jz7xvzsn....@sergiodj.net>
and subject line Re: Bug#1079874: valgrind: FTBFS with mpich instead of openmpi
has caused the Debian Bug report #1079874,
regarding valgrind: FTBFS with mpich instead of openmpi
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1079874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079874
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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.reproducible-builds.org/debian/rb-pkg/unstable/i386/valgrind.html
[2]
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/armhf/valgrind.html
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
checking secondary target for usable MPI2-compliant C compiler and mpi.h... no
--- End Message ---
--- Begin Message ---
On Saturday, April 05 2025, I wrote:
> On Tuesday, December 17 2024, Graham Inggs wrote:
>
>> On Tue, 17 Dec 2024 at 08:25, Emanuele Rocca <e...@debian.org> 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-17T09:04:47Z.build
>>>
>>> Can you please double-check once again?
>>
>> Indeed, on reproducible builds it seems valgrind now builds
>> successfully in unstable, but still fails in trixie.
>>
>> I'm guessing something fixed between mpich 4.2.0-14 in trixie and
>> 4.2.1-4 in unstable.
>
> Hi,
>
> I see that valgrind is building fine in trixie on armhf and other
> arches. It is not reproducible, but that's another issue.
>
> Should this bug be closed?
I'm taking the liberty of closing it. Please reopen if it's still
applicable.
Cheers,
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/
signature.asc
Description: PGP signature
--- End Message ---
