On Sun, Jan 20, 2013, Jason Swails wrote:
> I think it's fairly trivial to get configure to
> obey MPI_HOME (and specify a full path to mpif90/mpicc inside config.h,
> etc.) or other common environment variables (e.g., CC, FC, F90, CFLAGS,
> FFLAGS, etc.).
I think it makes sense to require MPI_HOME to be set for an mpi build,
and to put the full path inside config.h. The usual assumption is that
the appropriate libraries are either (a) in $MPI_HOME/lib or $MPI_HOME/lib64;
or (b) in someplace where mpif90 knows how to find them, and won't be misled
by anything appearing in these default locations.
But I don't know that all mpi installations have such an MPI_HOME location,
such that the executables are in $MPI_HOME/bin. In some cases we may just
have to tell users to hand-edit config.h.
...dac
_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers
Received on Sun Jan 20 2013 - 17:30:04 PST
