[mvapich-discuss] Trouble compiling MVAPICH2 1.9

[Jonathan Perkins]

On Tue, May 21, 2013 at 04:37:30PM +0200, Jens Glaser wrote:
> Hi,
> 
> I've downloaded the tarball for MVAPICH2 1.9, and tried to compile. Unfortunately, compilation does not complete,
> it aborts with error, rather at the end of the compilation.
> 
> [..] 
>  F77      src/binding/f77/setbotf.lo
>   CC       src/mpid/ch3/channels/common/src/affinity/hwloc_bind.lo
>   CCLD     libch3affinity.la
>   GEN      lib/libmpich.la
> /usr/bin/ld: src/mpi/romio/.libs/libromio.a(close.o): relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC
> src/mpi/romio/.libs/libromio.a(close.o): could not read symbols: Bad value
> collect2: ld returned 1 exit status
> make[2]: *** [lib/libmpich.la] Error 1
> rm src/mpid/ch3/channels/mrail/src/cuda/pack_unpack.cpp
> make[2]: Leaving directory `/lustre/medusa/jglaser/mvapich2-1.9'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/lustre/medusa/jglaser/mvapich2-1.9'
> make: *** [all] Error 2
> 
> To reproduce, I did 
> 
> export F90=
> export F90FLAGS=
> ./configure --with-cuda=/sw/kfs/cuda/5.0/linux_binary/ --enable-cuda --enable-shared --prefix=/nics/d/home/jglaser/local-kf --with-torque=/opt/torque/default/
> make
> 
> Previous versions (1.9a2) built fine on the machine (keeneland KFS) I am using.
> 
> I can provide the full compilation output and the config.log file upon request.
> Did I do anything wrong?

This is most likely an issue of previous static build not cleaned up
properly before a new attempt at a shared build.  Can you remove your
build directory and freshly extract the tarball to see if this is the
case?

-- 
Jonathan Perkins
http://www.cse.ohio-state.edu/~perkinjo