[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
Wed Oct 30 09:24:13 CDT 2013


On Wed, 30 Oct 2013, Matthew Knepley wrote:

> On Wed, Oct 30, 2013 at 3:09 AM, Satish Balay <balay at mcs.anl.gov> wrote:
> 
> > On Tue, 29 Oct 2013, Jed Brown wrote:
> >
> > > >    So how about just moving externalpackages into $PETSC_ARCH and
> > > >    don’t build some elaborate scheme that reuses tar balls for a tiny
> > > >    number of people.  In other words a clean truly means clean and
> > > >    gets new tar balls.
> > >
> > > That sounds good to me.
> >
> > I've attempted to move externalpackages into PETSC_ARCH.
> > But I need to figureout how to do this for blaslapack.py & mpi.py - as they
> > don't use the regular package.py stuff..
> >
> > Matt - any ideas? The commits I have are:
> >
> 
> Those are good. I think we bite the bullet and finally convert those two to
> use
> package.py. It will suck for a while.

Ah - it was failing for all packages in
BuildSystem/cofig/packages/*.py - and now I see a typo during
copy/paste. Its fixed now.

Satish


More information about the petsc-dev mailing list