[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 Tue, 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
> 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.
>

If we are hashing the source, why ever keep it around? Just keep the hash.
If
the hash does not match the tarball we get (either from options or by
default lookup),
unpack it, build it, and store that hash, then delete the source.

   Matt

-- 
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/20131029/2df796b8/attachment.html>