Addendum:
I have LAM/MPI 7.1.4 from July 24, 2007.
Zachary Levine
Physicist, NIST
From: Levine, Zachary
Sent: Wednesday, May 14, 2008 5:29 PM
To: '[email protected]'
Cc: '[EMAIL PROTECTED]'
Subject: installation help offered and requested
I am trying to install the parallel version of MIT Photonic Bands on a Red Hat
Linux system 2.6.18-53.1.14.el5 x86_64. I have two processors locally in one
computer (and lots more in our central cluster). I managed to get the serial
version working on this machine, except I didn't figure out how to link in HDF5.
I got stuck installing FFTW. At first, I wasn't able to get past the
"./configure" step. Then, one of our local gurus advised me to do the
following:
setenv MPICC /local/apps/lam/bin/mpicc
setenv MPILIBS "-L/local/apps/lam/lib -lmpi -llam"
./configure --enable-mpi
make
(Of course, I had to adjust /local/apps/lam/bin to match where my file mpicc
was, and similarly /local/apps/lam was matched. Also, I used bash so the
syntax was slightly different.)
Now, my guru had to pick this out of the configure file, which I have a lot of
trouble reading, and he says it isn't in the documentation or the FAQs for
FFTW, so maybe this could be viewed as a contribution. (Sorry this posting
isn't to FFTW, but I couldn't figure out how to get on the list over there!)
This worked to a certain extent. The "./configure" step completed
successfully, which is better than without MPICC and MPILIBS set. However, the
"make" step failed. After using locate to find some other versions of the
libraries, I was left with the following message at the end of the "make" step.
/bin/sh ../libtool --mode=link /usr/bin/mpicc -O3 -fomit-frame-pointer
-fno-schedule-insns -fschedule-insns2 -fstrict-aliasing -L/usr/local/lib
-L/usr/local/szip2.0-linux-gcc3.2.3-enc/lib -L/usr/lib64/ruby/1.8/x86_64-linux/
-o test_sched test_sched.o libfftw_mpi.la ../fftw/libfftw.la -L/usr/lib
-L/lib64 -L/usr/lib/x86_64-redhat-linux4E/lib64 -L/lib
-L/usr/lib/i386-radhat-linux4E/lib -lmpi -llam -llammpio -lm /usr/bin/mpicc -O3
-fomit-frame-pointer -fno-schedule-insns -fschedule-insns2 -fstrict-aliasing -o
test_sched test_sched.o -L/usr/local/lib
-L/usr/local/szip2.0-linux-gcc3.2.3-enc/lib -L/usr/lib64/ruby/1.8/x86_64-linux/
./.libs/libfftw_mpi.a ../fftw/.libs/libfftw.a -L/usr/lib -L/lib64
-L/usr/lib/x86_64-redhat-linux4E/lib64 -L/lib
-L/usr/lib/i386-radhat-linux4E/lib /usr/lib/libmpi.a /usr/lib/liblam.a -ldl
-llammpio -lm
/usr/bin/ld: skipping incompatible /usr/lib/libdl.so when searching for -ldl
/usr/bin/ld: skipping incompatible /usr/lib/libdl.a when searching for -ldl
/usr/bin/ld: skipping incompatible /usr/lib/liblammpio.a when searching for
-llammpio
/usr/bin/ld: skipping incompatible /usr/lib/liblammpio.a when searching for
-llammpio
/usr/bin/ld: cannot find -llammpio
collect2: ld returned 1 exit status
/usr/bin/mpicc: No such file or directory
make[1]: *** [test_sched] Error 1
make[1]: Leaving directory `/local/home/zlevine/Code/FFTW/fftw-2.1.5/mpi'
make: *** [all-recursive] Error 1
So which version of lam is required? Presumably lam generates lammpio.a. I
don't know which version of lam I have, but the latest components appear to
have been written on 2005/12/18.
Please advise.
Thank you,
Zachary Levine
Physicist, NIST
_______________________________________________
mpb-discuss mailing list
[email protected]
http://ab-initio.mit.edu/cgi-bin/mailman/listinfo/mpb-discuss
