[petsc-dev] [petsc-maint] valgrind detected on /usr/local/include and enabled but header files from this dir are not added to build path

Satish Balay balay at mcs.anl.gov
Tue Oct 29 14:47:01 CDT 2013


On Tue, 29 Oct 2013, Jed Brown wrote:

> Satish Balay <balay at mcs.anl.gov> writes:
> > At least for configure.log - there is a chicken-egg problem with
> > PETSC_ARCH determined by configure. Perhaps it can be delt with
> > easily..
> 
> How long does it take to determine a suitable PETSC_ARCH?  Can't we
> buffer and spew to the screen if we fail before getting that far?


If you look at the current configure.log - its after fortran compiler
detection.

Currently the dependencies [for PETSC_ARCH] are:

    self.petscdir = framework.require('PETSc.utilities.petscdir', self)
    self.languages = framework.require('PETSc.utilities.languages', self)
    self.compilerFlags = framework.require('config.compilerFlags', self)

so it need to get that far before PETSC_ARCH can be set/used..

Satish



More information about the petsc-dev mailing list