Dear Johannes,
if you use a compiler suite that include both f77 and f90, the fortran
bindings created by LAM building process have a good chance to be valid
for both compilers, the only difference in compiling should be the
executable to be invoked (e.g. xlf90 rather than xlf77), but I am afraid
that this is hardwired in mpif77 after building; however f90 syntax is
almost completely backward compatible with f77, so I think that the best
way in your case is to configure and build with the f90 compiler, then
you could use the mpif77 (you can move/link it to mpif90 if you prefer)
to compile sources in both languages. It is not optimal but it works for me.
Any other option?
bye, Davide
jnt7 ha scritto:
> Dear readers
>
> Could anyone point me in the right direction if I want to include F90 as well
> as F77 bindings in Lam-
> mpi? I have a large NASA code that consists of mixed F77, F90 and C code. This
>...
> usysv and sysv rpi modules. I am able to build LAM nicely with
>
> export CC=/usr/bin/gcc
> export CFLAGS="-O3 -mpowerpc-gpopt -mpowerpc64"
> export CPP=/usr/bin/cpp
> export CPPFLAGS=""
> export CXX=/usr/bin/g++
> export FC=/opt/ibmcmp/xlf/8.1/bin/xlf
> export FFLAGS="-qextname"
>
> ./configure --without-dash-pthread --with-purify --with-rpi=usysv
> --prefix=/usr/local/lam
>
> However, only mpif77 appears in my lam bin directory, and obviously the F90
> bindings were not made.
> If I use FC=xlf90, then F77 bindings won't be made... (correct?).
>
> MPICH allows one to make bindings for both; does anyone know if this is
> possible in LAM as well?
>
--
__________________________________________________________
Davide Cesari ARPA-Servizio Idro Meteorologico __
www http://www.arpa.emr.it/sim ---
Address: ARPA-SIM, Viale Silvani 6, 40122 Bologna, Italy
__________________________________________________________
|
