Hello, This is interesting, as we don't see this error when using mpich on OSX. I notice you are using openmpi-3.1.3. It is worth mentioning that there are known data corruption issues with openmpi 3.1.3 and 4.0 and HDF5 1.10.x, as documented here: https://portal.hdfgroup.org/display/knowledge/OpenMPI+Build+Issues. I've installed 1.10.1 using openmpi on my OSX machine, using openmpi 3.1.3 as provided by the 'homebrew' package management system, and am unable to duplicate this issue. I built and installed hdf5 using this version of openmpi with no immediate ill effect, and building the most recent `master` from github wasn't a problem. You might try building hdf5 from scratch instead of installing it with your package manager (I believe you are using macports?). If that doesn't solve the problem, or if you'd rather ask on the mailing list, you can find information to join the netCDF mailing list here: https://www.unidata.ucar.edu/software/netcdf/mailing-lists.html I hope this helps! -Ward > Hoping to find out why I am getting: > > In file included from > /Users/cary/projects/ulixesall-llvm/netcdfc/libdispatch/dvarinq.c:11: > In file included from > /opt/contrib-llvm7_appleclang/hdf5-1.10.1-par/include/hdf5.h:22: > In file included from > /opt/contrib-llvm7_appleclang/hdf5-1.10.1-par/include/H5public.h:59: > /opt/contrib-llvm7_appleclang/openmpi-3.1.3-nodl/include/mpi.h:327:37: > error: typedef redefinition with different types ('struct > ompi_communicator_t *' vs 'int') > typedef struct ompi_communicator_t *MPI_Comm; > ÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂÂ ^ > /Users/cary/projects/ulixesall-llvm/netcdfc/include/ncdispatch.h:88:13: > note: previous definition is here > typedef int MPI_Comm; > ÂÂÂÂÂÂÂÂÂÂÂ ^ > > > with netcdf-c, from github. > > Thx...John Cary > > Ticket Details =================== Ticket ID: EKV-496024 Department: Support netCDF Priority: Normal Status: Closed =================== NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.