On Fri, Jul 31, 2015 at 8:51 AM, Xujun Zhao <xzha...@gmail.com> wrote:
> Here is the summary of the output, and the complete log file is attached. > One thing to note is that HDF5 and NetCDF4 were found during your configure: configure:36706: checking hdf5.h presence configure:36706: mpicc -E conftest.c configure:36706: $? = 0 configure:36706: result: yes configure:36706: checking for hdf5.h configure:36706: result: yes configure:36721: checking for hdf5 - version >= 1.8.0 configure:36775: mpicc -c conftest.c >&5 configure:36775: $? = 0 configure:36777: result: yes configure:36810: checking for H5Fopen in -lhdf5 configure:36835: mpicc -o conftest conftest.c -lhdf5 >&5 configure:36835: $? = 0 configure:36844: result: yes configure:36911: result: <<< Configuring library with HDF5 support >>> configure:36988: result: <<< Configuring library with NetCDF version 4 support >>> configure:37091: result: <<< Configuring library with Exodus version v5.22 support >>> configure:37106: result: <<< Configuring library with Exodus Fortran API >>> configure:37210: result: <<< Configuring library with Nemesis version v5.22 support >>> configure:37284: result: <<< Configuring library with libHilbert support >>> I think this means that Exodus will use NetCDF4/HDF5, at least according to this note in contrib/exodusii/5.22b/exodus/Makefile.standalone: # Set this to yes if your netcdf is compiled with the netcdf4 extensions # which require linking with hdf5. It is assumed that the netcdf and hdf5 # library and include paths are the same. Since your segfault is limited to writing Exodus files, I'd first try building libmesh with HDF5 explicitly disabled (--disable-hdf5) and see if that fixes it. This is a configuration that doesn't get tested very often, and may just not be working. -- John ------------------------------------------------------------------------------ _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
