[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 13:51:57 CDT 2013
Barry Smith <bsmith at mcs.anl.gov> writes:
> 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.
People will complain when they have to download the same tarball many
times. But I don't especially care as long as the builds are done
inside $PETSC_ARCH instead of in a common place. (This is also useful
when building multiple configurations of PETSc in parallel.)
-------------- 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/dd42a127/attachment.sig>
More information about the petsc-dev
mailing list