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

[Matthew Knepley]

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.

   Matt


>
> https://bitbucket.org/petsc/petsc/commits/6169ffbf03ec9c2d2c66d78de2f75db3c481fc23?at=master
>
> https://bitbucket.org/petsc/petsc/commits/315689470ef34fb0770466bd7f1fae35d41712f8?at=master
>
> BTW: would we still keep --with-externalpackages-dir option in this scheme?
>
> thanks,
> Satish
>



-- 
What most experimenters take for granted before they begin their
experiments is infinitely more interesting than any results to which their
experiments lead.
-- Norbert Wiener
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20131030/33edc6ae/attachment.html>