[petsc-dev] [petsc-maint] valgrind detected on /usr/local/include and enabled but header files from this dir are not added to build path
Jed Brown
jedbrown at mcs.anl.gov
Tue Oct 29 09:04:31 CDT 2013
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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20131029/fe96a247/attachment.sig>
More information about the petsc-dev
mailing list