[mpich-discuss] static compiling with mpich2

[Dave Goodell]

We (the MPICH2 developers) primarily compile statically and we  
definitely use static libraries in many of our nightly tests.  GCC is  
also well tested with MPICH2 and is totally compatible on most  
platforms.

Have you used gdb or valgrind to determine where/why the segfault is  
occurring?

If the segfault is coming from within MPICH2, can you try configuring  
with "--enable-g=dbg --enable-error-checking" and *without* any "-- 
enable-fast" arguments?  Versions of MPICH2 built for performance are  
much less forgiving of errors in application code.

-Dave

On Jan 29, 2010, at 3:03 PM, Jason Palmer wrote:

> Hi all,
>
> We recently switched from Mpich1 to Mpich2 as part of a general  
> upgrade, and I’m re-building a program that was previously compiled  
> as a static binary under Mpich1 on 64-bit RedHat Linux using  
> pathscale fortran on an AMD Opteron cluster.
>
> We are now using gcc-4.4.3 (instead of pathscale), and I can compile  
> and run the code with dynamic libraries, but when I compile with – 
> static, the compile succeeds, but the binary gives a segmentation  
> fault when executed, with or without mpiexec.
>
> I have tried compiling Mpich2 (using gcc 4.4.3) both with –enable- 
> sharedlibs=gcc and without, but both give the error in the static  
> version but no error in the non-static version.
>
> Has anyone had success with static compiling of Mpich2 / gcc programs?
>
> Thanks,
> Jason
>
>
> _______________________________________________
> mpich-discuss mailing list
> mpich-discuss at mcs.anl.gov
> https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss