Re: [OMPI users] MPI_WAITANY compile error with mpi.mod vs. mpif.h on OS X

2015-07-27 Thread Ted Mansell
OK, finally got it. MPI_WAITALL gets MPI_STATUSES_IGNORE, but MPI_WAITANY gets MPI_STATUS_IGNORE. I'm otherwise familiar with just MPI_WAIT. Thanks again! - Ted On Jul 27, 2015, at 4:07 PM, Jeff Squyres (jsquyres) wrote: > On Jul 27, 2015, at 4:45 PM, Ted Mansell wrote: >> >> That was a fa

Re: [OMPI users] MPI_WAITANY compile error with mpi.mod vs. mpif.h on OS X

2015-07-27 Thread Jeff Squyres (jsquyres)
On Jul 27, 2015, at 4:45 PM, Ted Mansell wrote: > > That was a fast response! Of course, it's not my code :). :-) > I had looked at the arguments and thought they were OK, but eventually > noticed that the fourth argument is supposed to be an *array* of statuses. > Apparently passing 'MPI_STA

Re: [OMPI users] MPI_WAITANY compile error with mpi.mod vs. mpif.h on OS X

2015-07-27 Thread Ted Mansell
That was a fast response! Of course, it's not my code :). I had looked at the arguments and thought they were OK, but eventually noticed that the fourth argument is supposed to be an *array* of statuses. Apparently passing 'MPI_STATUS_IGNORE' there did not cause a problem for the 'mpif.h' interf

Re: [OMPI users] MPI_WAITANY compile error with mpi.mod vs. mpif.h on OS X

2015-07-27 Thread Jeff Squyres (jsquyres)
> On Jul 27, 2015, at 3:15 PM, Ted Mansell wrote: > > Hi, > > I'm getting a compile-time error on MPI_WAITALL and MPI_WAITANY when using > "use mpi": > > parcel.f90(555): error #6285: There is no matching specific subroutine for > this generic subroutine call. [MPI_WAITANY] > call