cannam@127: cannam@127: cannam@127: cannam@127: cannam@127:
cannam@127:cannam@127: Next: Linking and Initializing MPI FFTW, Previous: Distributed-memory FFTW with MPI, Up: Distributed-memory FFTW with MPI [Contents][Index]
cannam@127:All of the FFTW MPI code is located in the mpi
subdirectory of
cannam@127: the FFTW package. On Unix systems, the FFTW MPI libraries and header
cannam@127: files are automatically configured, compiled, and installed along with
cannam@127: the uniprocessor FFTW libraries simply by including
cannam@127: --enable-mpi
in the flags to the configure
script
cannam@127: (see Installation on Unix).
cannam@127:
cannam@127:
Any implementation of the MPI standard, version 1 or later, should
cannam@127: work with FFTW. The configure
script will attempt to
cannam@127: automatically detect how to compile and link code using your MPI
cannam@127: implementation. In some cases, especially if you have multiple
cannam@127: different MPI implementations installed or have an unusual MPI
cannam@127: software package, you may need to provide this information explicitly.
cannam@127:
Most commonly, one compiles MPI code by invoking a special compiler
cannam@127: command, typically mpicc
for C code. The configure
cannam@127: script knows the most common names for this command, but you can
cannam@127: specify the MPI compilation command explicitly by setting the
cannam@127: MPICC
variable, as in ‘./configure MPICC=mpicc ...’.
cannam@127:
cannam@127:
If, instead of a special compiler command, you need to link a certain
cannam@127: library, you can specify the link command via the MPILIBS
cannam@127: variable, as in ‘./configure MPILIBS=-lmpi ...’. Note that if
cannam@127: your MPI library is installed in a non-standard location (one the
cannam@127: compiler does not know about by default), you may also have to specify
cannam@127: the location of the library and header files via LDFLAGS
and
cannam@127: CPPFLAGS
variables, respectively, as in ‘./configure
cannam@127: LDFLAGS=-L/path/to/mpi/libs CPPFLAGS=-I/path/to/mpi/include ...’.
cannam@127: