[mpich-discuss] about installation

[Dave Goodell]

--enable-sharedlibs=BLAH is the old argument name that previously asked MPICH2 to build shared libraries.  It's still partially used, but it only indicates what style of shared libraries should be built instead of indicating whether they should be built.  "--enable-shared" is more in line with the way the rest of the world asks for shared library builds and using it simplifies the implementation of the hydra, MPL, and OPA subprojects of MPICH2.

In the new scheme, you should either pass "--enable-shared", "--enable-shared --enable-sharedlibs=BLAH", nothing, or "--disable-shared".  Other combinations are invalid.

Sorry for the confusion.  The "--enable-sharedlibs=BLAH" option will probably go away sometime this year.

-Dave

On Jun 28, 2011, at 12:56 PM CDT, Jain, Rohit wrote:

> Based on description, I figured I don't need --enabled-shared option. So, I removed it. 
> 	configure: error: --enable-sharedlibs cannot be used without --enable-shared
> 
> I noticed I have another option specified in earlier configuration: --enable-sharedlibs=gcc
> 
> Looking at README, it seems these shared options are also used to create shared mpich library, other than mentioned usage here for valgrind & debugging.
> 	
> Anyone has more details on it? 
> 
> -Rohit
> 
>> 
>> --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
> 
> _______________________________________________
> mpich-discuss mailing list
> mpich-discuss at mcs.anl.gov
> https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss