Hi,
On Mon, May 13, 2013 at 12:18 PM, Kshatresh Dutta Dubey
<kshatresh.gmail.com> wrote:
> /opt/software/mpich2/default//bin/mpicc -fPIC -fno-strict-aliasing -DNDEBUG
> -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
> --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC
> -I/usr/include/python2.4 -c src/MPI.c -o
> build/temp.linux-x86_64-2.4/src/MPI.o
> /opt/software/mpich2/default//bin/mpicc -shared
> build/temp.linux-x86_64-2.4/src/MPI.o -o
> build/lib.linux-x86_64-2.4/mpi4py/MPI.so
> /usr/bin/ld:
> /opt/software/mpich2/default/lib/libmpich.a(comm_create_keyval.o):
> relocation R_X86_64_32 against `a local symbol' can not be used when making
> a shared object; recompile with -fPIC
> /opt/software/mpich2/default/lib/libmpich.a: could not read symbols: Bad
> value
I think the problem here is that your system mpich2 library
(libmpich.a) was built without position-independent code (i.e. the
-fPIC switch), perhaps because it was built only with static
libraries. I'd say your best bet would be to download mpich2 yourself
and use $AMBERHOME/AmberTools/src/configure_mpich to create your own
mpich2 installation in $AMBERHOME. An mpich2 installation created in
this way should give you no issues when compiling Amber.
Hope this helps,
-Dan
--
-------------------------
Daniel R. Roe, PhD
Department of Medicinal Chemistry
University of Utah
30 South 2000 East, Room 201
Salt Lake City, UT 84112-5820
http://home.chpc.utah.edu/~cheatham/
(801) 587-9652
(801) 585-9119 (Fax)
_______________________________________________
AMBER mailing list
AMBER.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber
Received on Mon May 13 2013 - 12:30:03 PDT
