[mvapich-discuss] Error while compiling mpi4py with MVAPICH

[Jonathan Perkins]

On Wed, Sep 29, 2010 at 1:46 PM,  <senthil.natesan at ndsu.edu> wrote:
> Dear MVAPICH developers,
>
> I am trying to compile mpi4py to run an python application (MMPBSA.py from
> AMBER molecular dynamics package). I have successfully compiled it on
> MPICH2 and now I am trying to compile with MVAPICH, but it shows the
> following error. I have MVAPICH2-1.5 installed here and it works well for
> other applications.
>
> Here I am showing the end of the output (showing error)
> ------------------------------------------------------------------
> building 'mpi4py.MPI' extension
> creating build/temp.linux-x86_64-2.7
> creating build/temp.linux-x86_64-2.7/src
> /usr/mpi/gcc/mvapich2-1.5/bin/mpicc -fPIC -fno-strict-aliasing -DNDEBUG -g
> -fwrapv -O3 -Wall -Wstrict-prototypes -I/usr/local/include/python2.7 -c
> src/MPI.c -o build/temp.linux-x86_64-2.7/src/MPI.o
> /usr/mpi/gcc/mvapich2-1.5/bin/mpicc -shared
> build/temp.linux-x86_64-2.7/src/MPI.o -o
> build/lib.linux-x86_64-2.7/mpi4py/MPI.so
> /usr/bin/ld:
> /usr/mpi/gcc/mvapich2-1.5/lib/libmpich.a(comm_create_keyval.o): relocation
> R_X86_64_32 against `MPID_Keyval_mem' can not be used when making a shared
> object; recompile with -fPIC
> /usr/mpi/gcc/mvapich2-1.5/lib/libmpich.a: could not read symbols: Bad value
> collect2: ld returned 1 exit status
> error: command '/usr/mpi/gcc/mvapich2-1.5/bin/mpicc' failed with exit
> status 1

It looks like you're trying to create a shared library using objects
that were not compiled with -fPIC in the static libmpich.a library.
You may have a bug that was fixed with the mvapich2-1.5.1p1 release.
Please install this version and see if you still encounter this issue.

For your convenience:
http://mvapich.cse.ohio-state.edu/download/mvapich2/mvapich2-1.5.1p1.tgz

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