Fortran 90 and BeoMPI
bogdan.costescu at iwr.uni-heidelberg.de
Wed Mar 14 07:28:09 PST 2001
On Wed, 14 Mar 2001, Daniel Ridge wrote:
> ... I would suggest that people who would be in a
> position to require per-platform wranglings for MPI often also need to
> perform similar wranglings to accomodate differences in the C library
> or in the Fortran environment. MPI compiler wrappers hardly seem like
> the right place to accomodate these per-platform differences.
I'd like to disagree 8-)
I have here 2 clusters, one running jobs on top of LAM-MPI and the other
running jobs on top of MPICH on top of SCore. By using mpifxx, I'm able to
compile things without knowing where the include and lib files are and
even more without knowing which is the right order of linking the libs;
just try to do this by hand for LAM-MPI for example!
Another example is the 64 bit platforms where you can compile for both 32
and 64 bit by specifying a simple flag like -32 or -64. Doing linking by
hand means that _I_ have to choose the libraries and I might choose the
wrong one(s) ! Sometimes this is noticed by the linker, but not always...
> ./configure seems much more palatable than a per-library compiler
> wrappers. I've seen a number of apps that are MPI enabled and which
> supply a configure script which work just fine without using the
> compiler wrappers.
Of course, if every software package would be using ./configure,
everything would be easy. Try to convince the maintainers of big Fortran
packages like Gaussian or CHARMM to switch to ./configure 8-(
IWR - Interdisziplinaeres Zentrum fuer Wissenschaftliches Rechnen
Universitaet Heidelberg, INF 368, D-69120 Heidelberg, GERMANY
Telephone: +49 6221 54 8869, Telefax: +49 6221 54 8868
E-mail: Bogdan.Costescu at IWR.Uni-Heidelberg.De
More information about the Beowulf