As far as the MPI spec is concerned, you only need to include mpif.h and
define offsets as MPI_OFFSET_KIND. In older versions of some MPI
implementations you may need to do something else because the MPI-IO part
was not fully integrated with the implementation.
Rajeev
> Date: Fri, 27 Jan 2006 10:05:57 -0500
> From: "Barry A. Croker" <crokerba_at_[hidden]>
> Subject: Re: LAM: MPI I/O and NFS
> To: lam_at_[hidden]
> Message-ID: <DA98E810-A058-47BD-B363-BEF709D7C93C_at_[hidden]>
> Content-Type: text/plain; charset="us-ascii"
>
> David, others,
>
> This might be an indication of a larger misunderstanding, that maybe
> you can help with. The documentation that I have is not entirely
> clear about some of the included header files needed for MPI I/O.
>
> For "normal" MPI programs I "INCLUDE mpif.h". When I started
> writing
> the MPI I/O routines on my local machine (using LAM-MPI) I
> found that
> I also had to "INCLUDE mpiof.h" for everything to be recognized.
> However, even with both of these includeded I still get "Entity
> mpi_offset_kind has undefined type", so I didn't use it (bad call I
> guess). When I ported our code to other platforms, I had to modify
> these include statements. For example, the MPICH-2
> distribution gave
> me redundant declaration errors when I included both, but no
> complaints when I only "INCLUDE mpif.h". Likewise, the IBM SP4 had
> similar behavior.
>
> Is there something incorrect with my installation of MPI? Should I
> need both headers, or only one? The odd thing is the only time that
> MPI I/O appears to work correct is on my local machine, when I
> include both files.
>
> Thanks for everyone's help and patience with this issue.
>
> David Cronk wrote:
>
> >Barry,
>
> >try INTEGER(KIND=MPI_OFFSET_KIND) offset, disp
>
> >I am guessing your INTEGER is 32 bits while MPI requires 64 bits for
> >offset and displacement (files are often larger than 2 gig).
>
> >Dave.
|
