Hi,

we are compiling and running with an mpich configured with "--enable-g=dbg,meminit" option, we have installed valgrind-devel package.

Configuring MPICH version 4.2.2 with  '--prefix=/opt/mpi/mpich-4.2.2-debug' '--enable-debuginfo' '--enable-g=dbg,meminit' 'CC=/usr/bin/gcc' 'CXX=/usr/bin/g++' 'FC=/usr/bin/gfortran' 'F77=/usr/bin/gfortran' '--with-device=ch3:sock' '--enable-romio'

We saw there are some valgrind suppression files into de repo but they are not "installed" when we launch a "make install".

find . -name "*valg*"
./modules/hwloc/contrib/hwloc-valgrind.supp
./modules/ucx/contrib/valgrind.supp
./src/pm/hydra/modules/hwloc/contrib/hwloc-valgrind.supp

Is this normal?

Mpich finds valgrind headers:

checking valgrind/valgrind.h usability... yes
checking valgrind/valgrind.h presence... yes
checking for valgrind/valgrind.h... yes
checking valgrind/memcheck.h usability... yes
checking valgrind/memcheck.h presence... yes
checking for valgrind/memcheck.h... yes
checking helgrind.h usability... no
checking helgrind.h presence... no
checking for helgrind.h... no
checking valgrind/helgrind.h usability... yes
checking valgrind/helgrind.h presence... yes
checking for valgrind/helgrind.h... yes
checking drd.h usability... no
checking drd.h presence... no
checking for drd.h... no
checking valgrind/drd.h usability... yes
checking valgrind/drd.h presence... yes
checking for valgrind/drd.h... yes
checking whether the valgrind headers are broken or too old... no

I also found this in src/pm/hydra/modules/hwloc/Makefile.in

# Only install the valgrind suppressions file if we're building in
# standalone mode
@HWLOC_BUILD_STANDALONE_TRUE@dist_pkgdata_DATA = contrib/hwloc-valgrind.supp
all: all-recursive

What is the "standalone mode" ?

Thanks,

Eric

-- 
Eric Chamberland, ing., M. Ing
Professionnel de recherche
GIREF/Université Laval
(418) 656-2131 poste 41 22 42