Fortran 90 and BeoMPI

Joe Griffin joe.griffin at
Wed Mar 14 07:41:16 PST 2001

If I may add my 2 cents:

I like using mpifxx.  However, I REALLY disdain the fact
that vendors put their scripts in /usr/bin.  mpirun is
put in /usr/bin by several vendors.  I would rather the
vendors put files in /usr/local/PRODUCT. 

We have had mpich, mpipro, and LAM/MPI all on the
same platform, and things really get confusing.
Trying to determine what file is in /usr/lib/libmpipro.a
is not a good use of time.

As far as IA64 goes.  I think setting parameters such as:

setenv IA64ROOT        /usr/local/compiler50/ia64
setenv GCCROOT         /usr/local/compiler50/ia64

Should be done my the efc and ecc wrapper, and not
by the .csrhc and/or .profile files.

Joe Griffin

Bogdan Costescu wrote:
> 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-(
> Sincerely,
> Bogdan Costescu
> 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
> _______________________________________________
> Beowulf mailing list, Beowulf at
> To change your subscription (digest mode or unsubscribe) visit

More information about the Beowulf mailing list