There isn’t a lot of logic behind what gets updated when beyond “as necessary”. The most recent netcdf update fixed an issue with writing hdf5 files for us. I didn’t update exodusII at the time since it there was no specific issue that needed to be addressed, but it is quite old relative to what’s available on github, so it should probably be done at some point.
> On Jul 14, 2019, at 4:35 PM, Alexander Lindsay <alexlindsay...@gmail.com> > wrote: > > So I didn't get any replies to this, but now I'm getting more curious. I'm > curious why we fairly consistently update our netcdf version, but seem to > never update our exodusii contrib? Are we sure that everything is compatible? > I ran `make check` on my personal build of netcdf 4.6.2 with hdf5-1.10.5 and > all tests pass, so I'm wondering whether the incompatibility may be at a > higher level? Is our older exodusii source using "incorrect" APIs in the > newer netcdf versions when hdf5 is available? > > I can look this up, but what does netcdf do differently when hdf5 is or is > not enabled in our configure? > _______________________________________________ > Libmesh-devel mailing list > Libmesh-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/libmesh-devel
_______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
