Due to the current gap in continued funding from the U.S. National Science Foundation (NSF), the NSF Unidata Program Center has temporarily paused most operations. See NSF Unidata Pause in Most Operations for details.
Due to the current gap in continued funding from the U.S. National Science Foundation (NSF), the NSF Unidata Program Center has temporarily paused most operations. See NSF Unidata Pause in Most Operations for details.
On Tue, Oct 06, 2009 at 10:25:01AM -0600, Dennis Heimbigner wrote: > If you write a program that includes > mpi.h then indeed you will get conflicts; > so the question is: why are you including > mpi.h in your netcf programs? Does it work > ok if you remove the '#include <mpi.h>' ? Here's what we do in pnetcdf. Any place that pnetcdf needs MPI data structures, we include <mpi.h> we do not, however, include mpi.h in the pnetcdf.h header file. Because the pnetcdf API uses things like communicators and MPI info values, we force the caller to include mpi.h before including pnetcdf.h Our job is easier because we are always parallel, whereas netcdf-4 might not have parallel I/O support if the underlying HDF5 library does not have it. ==rob -- Rob Latham Mathematics and Computer Science Division Argonne National Lab, IL USA
netcdfgroup archives: