[petsc-dev] horrible CRAP in Configure.py

This is horrible, no extensible stuff in Configure.py; can't this be fixed to not requiring information about all these packages into the PETSc Configure? Thanks Barry self.umfpack = framework.require('config.packages.UMFPACK',self) self.umfpack.archProvider

[petsc-dev] Fwd: [petsc-maint #48974] petsc-dev configure unable to locate cholmod package

fig/BuildSystem > hg pull -u > cd $PETSC_DIR > ./configure > > Sean -- next part -- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20100706/3d1f83de/attachment.html>

[petsc-dev] [petsc-maint #49008] Problems with VecDotNorm2

On Jul 6, 2010, at 9:49 AM, Jose E. Roman wrote: > Dear all, > > We at SLEPc have included a custom implementation of vectors that emulates > block vectors in the spirit of PetscExt: v=[v1' v2']' where v1 and v2 are > PETSc vectors. This is required for some new SLEPc solvers. With this new >

[petsc-dev] meaning of VecScale() if not a collective

ore 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/20100706/bdd15620/attachment.html>