Re: building petsc 3.7.0: python can't pickle file objects

[Drew Parsons <dparsons@debian.org>]

On Fri, 2016-05-13 at 10:08 +0200, Johannes Ring wrote:
> On Fri, May 13, 2016 at 3:45 AM, Drew Parsons <apps@emerall.com>
> wrote:
...
> > Can anyone make sense of this error?  A simple configure (just
> > ./configure) does complete successfully, so it's some problem in
> > the
> > complex configure line that we're using. But I don't know which
> > term is
> > causing the problem.
> The problem is the "--useThreads 0" flag. Replacing it with
> "--useThreads=0" fixes the problem. 

Well damn. That sure is a weird thing to fail on. Thanks Johannes :)


> The build now fails for me with:
> 
> /tmp/src/petsc/src/mat/impls/aij/seq/superlu/superlu.c: In function
> ‘PetscErrorCode MatLUFactorNumeric_SuperLU(Mat, Mat, const
> MatFactorInfo*)’:
> /tmp/src/petsc/src/mat/impls/aij/seq/superlu/superlu.c:181:294:
> error:
> cannot convert ‘GlobalLU_t*’ to ‘mem_usage_t*’ for argument ‘19’ to
...
> Probably too old superlu?


Could well be. Our superlu is 4.3, upstream is already on 5.2.
Sébastien, are you available for updating superlu?

> > 
> > Has anyone started using petsc 3.7 for themselves yet?
> I haven't used petsc 3.7 yet, but we are testing dolfin-dev against
> petsc-dev, so the next release of dolfin should work fine with petsc
> 3.7. We expect to make the next release of dolfin before the summer.

Great! Thanks again Johannes.

Drew