I assume that your ring_f90 program is using the statement "use f90"?
(is that the OMPI example ring_f90 program?) If so, can you verify
that the compiler is picking up the OMPI f90 module and not some other
module? That would be my best guess for why it's acting wonky (e.g.,
if it gets into MPI_Comm_rank with a bogus communicator value).
On Feb 24, 2008, at 3:37 PM, Gregory J. Orris wrote:
Hey,
Been trying to activate mpif90 on a set of machines running Leopard
for some colleagues and have gotten stuck.
Compiles fine, but will not run any examples and returns
mymachine me% /usr/local/mpiexec -np 2 ./ring_f90
[mymachine.local:23974] *** An error occurred in MPI_Comm_rank
[mymachine.local:23974] *** on communicator MPI_COMM_WORLD
[mymachine.local:23974] *** MPI_ERR_COMM: invalid communicator
[mymachine.local:23974] *** MPI_ERRORS_ARE_FATAL (goodbye)
[mymachine.local:23975] *** An error occurred in MPI_Comm_rank
[mymachine.local:23975] *** on communicator MPI_COMM_WORLD
[mymachine.local:23975] *** MPI_ERR_COMM: invalid communicator
[mymachine.local:23975] *** MPI_ERRORS_ARE_FATAL (goodbye)
Seems tied up in how gfortran implements parameters. If MPI_COMM_WORLD
is changed in the example code to 0 (its parameter value) all is fine.
In the recesses of my mind I seem to remember reading ones that
gfortran used for f90 treats parameters differently than integers.
Anyone else seen this?
BTW mpif77 works without problems.
Regards,
Greg
_______________________________________________
users mailing list
us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/users
--
Jeff Squyres
Cisco Systems
