FYI, the PETSc tests that use MOAB passed using MOAB commit f862b4c on my laptop, though when I had mpich debugging on there looks like there may have been some memory leaks that don't appear in other PETSc tests. (log attached) Cheers, Toby On Wed, Feb 01, 2017 at 03:22:18AM +0530, Vijay S. Mahadevan wrote:
Toby, thanks for the update. Yes, I recently updated the "petsc" branch in MOAB to make sure that v4.9.2 is merged. Some of these changes are needed for one of my upcoming PR's to improve DMMoab support. I however have been on some international travel and haven't found enough time to take care of this.
Iulian, can you create a tarball that corresponds to the HEAD in petsc branch (if not already available from the ftp site) ?
Vijay
PS: The macports errors are related to ESMF. They have their custom version of MOAB (4.6.x) and so I'm unsure whether the port needs the latest MOAB as its dependency.
On Wed, Feb 1, 2017 at 3:07 AM, Tobin Isaac <[email protected]> wrote:
The commit of MOAB that we use in MAOB.py doesn't compile in gcc6 due to c++14 compatibility issues [1]. I checked out the latest petsc branch from their repo and it seems to compile. Can we ask them to host an updated tarball, too?
[1] https://trac.macports.org/ticket/52427#comment:2
Toby