[mpich-discuss] about installation

[Dave Goodell]

[I also answered this on the valgrind-users list, posting here for the MPICH2 community's benefit]

If you are trying to trace application calls to the MPI library, then rebuild your MPICH2 installation with the "--enable-shared" configure flag.  MPICH2 does not build shared libraries by default, but the Valgrind MPI wrappers expect a shared library in order to build.

If you are trying to trace calls *within* MPICH2, you can probably just reconfigure Valgrind with "--without-mpicc".

-Dave

On Apr 21, 2011, at 2:49 AM CDT, Kaveri Zanje wrote:

> I have install mpich2-1.3.2p1  with file system luster , testfs, ufs.
> I want to install valgrind for tracing MPI-IO call, but i am not able to install it .
> it is giving me following error
> 
> Making all in mpi
> make[2]: Entering directory `/home1/stu2/valgrind-3.6.0/mpi'
> mpicc -g -O -fno-omit-frame-pointer -Wall -fpic -m64  -fpic -shared  -o libmpiwrap-amd64-linux.so libmpiwrap_amd64_linux_so-libmpiwrap.o  
> /usr/bin/ld: /home/stu2/home1/mpich2-install/lib/libmpich.a(comm_rank.o): relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC
> /home/stu2/home1/mpich2-install/lib/libmpich.a: could not read symbols: Bad value
> collect2: ld returned 1 exit status
> make[2]: *** [libmpiwrap-amd64-linux.so] Error 1
> make[2]: Leaving directory `/home1/stu2/valgrind-3.6.0/mpi'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home1/stu2/valgrind-3.6.0'
> make: *** [all] Error 2
> _______________________________________________
> mpich-discuss mailing list
> mpich-discuss at mcs.anl.gov
> https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss