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

[Barry Smith]

On Oct 29, 2013, at 9:04 AM, Jed Brown <jedbrown at mcs.anl.gov> wrote:

> Barry Smith <bsmith at mcs.anl.gov> writes:
>>    Could you please add a —with-clean (or better name?) option to ./configure that does the $PETSC_ARCH removal business? Then we can just run
>> 
>>    $PETSC_ARCH/conf/reconf*.py  —with-clean
> 
> I guess this also has to delete relevant parts of externalpackages to
> make sure the current version of packages get downloaded.
> 
> Part of me wants to put all the externalpackages inside $PETSC_ARCH
> because the source is usually smaller than the object files or the

   Or simpler just have the —with-clean nuke external packages; makes life easy.  By "store the tarballs in a common place” and SHA1 crap you are making the system more complicated to understand and maintain.


   Barry

> compiled binary, so we're not saving anything by unpacking in a common
> location.  We could store the tarballs in a common place and include
> their SHA1 in ${package}.py so that BuildSystem could match the correct
> tarball and unpack it cleanly.