Begin forwarded message:
> From: John Mousel <john.mousel at gmail.com> > Date: June 6, 2012 10:12:19 AM CDT > To: Jed Brown <jedbrown at mcs.anl.gov> > Cc: petsc-maint at mcs.anl.gov, petsc-dev at mcs.anl.gov > Subject: Re: [petsc-maint #119133] petsc-dev configure crash > Reply-To: petsc-maint at mcs.anl.gov, John Mousel <john.mousel at gmail.com> > > Thanks Jed. Somehow I forgot to put the post-pull in .hg/hgrc for that > build. With all the other unneeded bells and whistles in hg, why doesn't it have a mechanism where WE can put this post-pull business into the repository instead of telling each user to do that? Barry > > On Wed, Jun 6, 2012 at 10:03 AM, Jed Brown <jedbrown at mcs.anl.gov> wrote: > >> You need to pull BuildSystem. >> >> >> On Wed, Jun 6, 2012 at 10:00 AM, John Mousel <john.mousel at gmail.com>wrote: >> >>> I'm getting the following after pulling and reconfiguring: >>> >>> >>> =============================================================================== >>> Configuring PETSc to compile on your >>> system >>> >>> =============================================================================== >>> >>> =============================================================================== >>> >>> It appears you do not have valgrind installed on your >>> system. >>> >>> We HIGHLY recommend you install it from www.valgrind.org >>> Or install valgrind-devel or equivalent using your package >>> manager. >>> >>> Then rerun >>> ./configure >>> >>> =============================================================================== >>> >>> TESTING: configureRegression from >>> PETSc.utilities.Regression(config/PETSc/utilities/Regression.py:32) >>> >>> ******************************************************************************* >>> CONFIGURATION CRASH (Please send configure.log to >>> petsc-maint at mcs.anl.gov) >>> >>> ******************************************************************************* >>> >>> John >>> >>> >> >