[mpich-discuss] about installation

[Dave Goodell]

On Jun 27, 2011, at 5:03 PM CDT, Jain, Rohit wrote:

> Hi Dave,
> 
> I am configuring new installation, and looking at my current config options, and need some clarification.
> 
> --enable-shared: If I just want to run machine installed valgrind on my application, and trying to find issues back in MPICH code, do I need to use this option?

If you want to use the valgrind MPI wrappers, you will need to pass "--enable-shared".  However, you will probably also need to rebuild your valgrind copy after building MPICH2 then.  The valgrind MPI wrappers are only for debugging problems *above* MPICH2, so if you want to debug within MPICH2 then you do not need to enable shared libraries.

If you want to debug MPICH2 itself with valgrind then I recommend "--enable-g=meminit,dbg" at a minimum, and you may also want to add "mem" to that list: http://wiki.mcs.anl.gov/mpich2/index.php/Support_for_Debugging_Memory_Allocation

> --enable-totalview: If I just want to run totalview with my application and debug application's code, not inside MPICH code, Do I need to use this option?

I'm not 100% sure what this option does.  I _think_ that it causes additional helper code and shared libraries to be built with that allow Totalview to locate processes within an MPI job and inspect the message queues.  Specifying this option may also require you to build with shared libraries, but someone else might need to confirm that.

If you just want to attach to individual processes manually with Totalview, you may not need this option.

-Dave

> Regards,
> Rohit
> 
> 
> -----Original Message-----
> From: mpich-discuss-bounces at mcs.anl.gov [mailto:mpich-discuss-bounces at mcs.anl.gov] On Behalf Of Dave Goodell
> Sent: Thursday, April 21, 2011 7:43 AM
> To: mpich-discuss at mcs.anl.gov
> Subject: Re: [mpich-discuss] about installation
> 
> [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
> 
> _______________________________________________
> mpich-discuss mailing list
> mpich-discuss at mcs.anl.gov
> https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss
> _______________________________________________
> mpich-discuss mailing list
> mpich-discuss at mcs.anl.gov
> https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss