Re: [Valgrind-users] Valgrind MPI fails to build libmpiwrapers

[Dave G. <go...@mc...>]

On Jun 28, 2011, at 2:56 PM CDT, janjust wrote:

>    Thanks for the reply. ; Setting $MPI_CC="mpicc -noswitcherror" moved the
> build a bit further but it exited with a different error, this time:
> 
> -------
> make[2]: Entering directory
> `/autofs/na1_home/janjust/valgrind/valgrind_sources/valgrind_clean_src/mpi'
> mpicc -noswitcherror    -I../include  -g -O -fno-omit-frame-pointer -Wall
> -fpic -m64  -MT libmpiwrap_amd64_linux_so-libmpiwrap.o -MD -MP -MF
> .deps/libmpiwrap_amd64_linux_so-libmpiwrap.Tpo -c -o
> libmpiwrap_amd64_linux_so-libmpiwrap.o `test -f 'libmpiwrap.c' || echo
> './'`libmpiwrap.c
> pgcc-Warning-Unknown switch: -fno-omit-frame-pointer
> pgcc-Warning-Unknown switch: -Wall
> pgcc-Warning-Unknown switch: -MT
> pgcc-Warning-Unknown switch: -MP
> pgcc-Warning-Unknown switch: -MF
> pgcc-Error-Output would overwrite input file:
> libmpiwrap_amd64_linux_so-libmpiwrap.o
> make[2]: *** [libmpiwrap_amd64_linux_so-libmpiwrap.o] Error 1
> make[2]: Leaving directory
> `/autofs/na1_home/janjust/valgrind/valgrind_sources/valgrind_clean_src/mpi'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory
> `/autofs/na1_home/janjust/valgrind/valgrind_sources/valgrind_clean_src'
> make: *** [all] Error 2
> ----------

Hmm... not sure why that's happening.  It looks like a bad makefile recipe is getting generated somehow.  I'll poke at it when I get a little more time.

> You are correct my mpicc is wrapped around a pgi compiler, and if I unload
> the pgi module that is setting the env_vars to it, and use a module that
> sets gcc instead it doesn't recognize an MPI2-cc like compiler at all. 
> 
> As to your suggestion of using a different MPI built with GCC. Say I have my
> own locally compiled MPI library with GCC, how do I go about pointing
> valgrind to this version? 

Just configure Valgrind with "--with-mpicc=/path/to/my/mpicc", replacing "/path/to/my" appropriately.

-Dave