Re: [Valgrind-users] Missing the library file /lib/valgrind/libmpiwrap-<platform>.so

[Rambaks, A. <and...@rw...>]

Hi Simon,


thank you for your reply!


I didn't suspect a problem with the configuration script and I am relatively new to Linux, i.e. I am not that proficient in reading the terminal outputs yet. I will try a new installation later in the day and get back to you.


However I have a different question regarding the installation of Valgrind with OpenMPI. The configuration file of OpenMPI has a FLAG --with-valgrind (I think it got introduced with MPI 5.x.x, not quite sure), which only works if Valgrind is already installed. However, Valgrind cannot be configured with the flag --with-mpicc, if OpenMPI is not installed (interdependency?). Does this mean that I first have to install Valgrind, then install OpenMPI (--with-valgrind enabled) and then install Valgrind again with the flag --with-mpicc ?


With kind regards

Andris Rambaks

________________________________
Von: Simon Sobisch <sim...@gn...>
Gesendet: Donnerstag, 8. Februar 2024 19:49:27
An: Rambaks, Andris
Cc: val...@li...
Betreff: Re: [Valgrind-users] Missing the library file /lib/valgrind/libmpiwrap-<platform>.so

Am 08.02.2024 um 18:25 schrieb Rambaks, Andris:
> Dear community,
>
> I am trying to install Valgrind for use with Open MPI. However, my
> installation is missing the library file
> */lib/valgrind/**libmpiwrap-<platform>.so*. I did configure
> release 3.22.0 with the /--with-mpicc/ flag and successefully ran make
> and make install.
>
> I am running Ubuntu 22.04.3 LTS with Open MPI 5.0.2. I can't seem to
> find the problem; the config.log returns:
>
> configure:18197: checking for mpicc
> configure:18221: found /usr/local/bin/mpicc
> configure:18234: result: /usr/local/bin/mpicc
> configure:18319: checking primary target for usable MPI2-compliant C
> compiler and mpi.h
> configure:18347: yes -o conftest -g -O -fno-omit-frame-pointer -Wall
> -fpic -m64  -fpic -shared -m64 conftest.c  >&5
> yes: invalid option -- 'o'
> Try 'yes --help' for more information.
> configure:18347: $? = 1
> configure: failed program was:
> | /* confdefs.h */
>
> I would really appreciate the help.
>
> Kind regards
>
> Andris Rambaks

Hi Andris,

the problem is that configure was told that the name of the
MPI2-compliant C compiler is "yes".
As you didn't explicit specify this (at least not intended to), this is
(also) a problem of the configure script.

It does hint what happens in your case to the user, as configure --help
says
   --with-mpicc=           Specify name of MPI2-ised C compiler


You did specify --with-mpicc - per default that is identical to
--with-mpicc=yes (--without-mpicc would be resolved ti --with-mpicc=no),
and that's not checked in the configure script and used "as is".


So to work around that that:

a) either drop the option completely (configure should then find it on
    its own if it is named mpicc and somwehere in
        $PATH:/usr/lib/openmpi/bin:/usr/lib64/openmpi/bin
b) specify it explicit using its full path passed to --with-mpicc (sadly
    I couldn't find how that is called/to be installed in your
    environment).


To fix this, the configure script should:
* explicit check for both "yes" and "no" and raise a clear error
* possibly add more compiler names / paths to its list

How is the "MPI2-compliant C compiler" named on your system, and where
is it installed to?

Kind regards,
Simon