Re: [petsc-dev] memory leaks and other problems with cusp tests in master

2014-12-22 Thread Karl Rupp
Hi Barry, http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2014/12/20/examples_master_arch-cuda-double_bb-proxy.log I will have a look at it some time in January. I fear I won't find the time any earlier. Best regards, Karli

[petsc-dev] Fwd: [ideas-xsdk] common configure/cmake arguments for XSDK packages ready for testing

2014-12-22 Thread Barry Smith
Redirecting Jed's question specifically for PETSc configure. Can we/should we save the modules setting at configure time and then check them always at make time? Is some environmental variable set that has a unique value based on the modules loaded? If this is a common problem for us th

[petsc-dev] Sean is going to love this

2014-12-22 Thread Barry Smith
In the past we've been not particularly supportive of getting PETSc in Linux package systems, in fact we've been a bit antagonistic. We should change this. Barry

Re: [petsc-dev] Sean is going to love this

2014-12-22 Thread Sean Farley
Barry Smith writes: > In the past we've been not particularly supportive of getting PETSc in > Linux package systems, in fact we've been a bit antagonistic. We should > change this. Well, knock me over with a feather.

Re: [petsc-dev] Sean is going to love this

2014-12-22 Thread Matthew Knepley
On Mon, Dec 22, 2014 at 8:31 PM, Barry Smith wrote: > > > In the past we've been not particularly supportive of getting PETSc in > Linux package systems, in fact we've been a bit antagonistic. We should > change this. I have the same objection as before, namely that many of our users want ext

Re: [petsc-dev] Sean is going to love this

2014-12-22 Thread Sean Farley
Matthew Knepley writes: > On Mon, Dec 22, 2014 at 8:31 PM, Barry Smith wrote: >> >> >> In the past we've been not particularly supportive of getting PETSc in >> Linux package systems, in fact we've been a bit antagonistic. We should >> change this. > > > I have the same objection as before, n

Re: [petsc-dev] Sean is going to love this

2014-12-22 Thread Matthew Knepley
On Mon, Dec 22, 2014 at 9:51 PM, Sean Farley wrote: > > > Matthew Knepley writes: > > > On Mon, Dec 22, 2014 at 8:31 PM, Barry Smith wrote: > >> > >> > >> In the past we've been not particularly supportive of getting PETSc in > >> Linux package systems, in fact we've been a bit antagonistic. W

Re: [petsc-dev] Sean is going to love this

2014-12-22 Thread Satish Balay
On Mon, 22 Dec 2014, Matthew Knepley wrote: > On Mon, Dec 22, 2014 at 8:31 PM, Barry Smith wrote: > > > > > > In the past we've been not particularly supportive of getting PETSc in > > Linux package systems, in fact we've been a bit antagonistic. We should > > change this. > > > I have the s

Re: [petsc-dev] Sean is going to love this

2014-12-22 Thread Jed Brown
Sean Farley writes: > The only way to do this, in my experience, is if the package manager has > something like 'variants' (macports and homebrew have it, at least, I > don't know about others): > > port install petsc +superlu +mumps +mpich +hdf5 +hypre ... etc. I think variants are a crutch for

Re: [petsc-dev] Sean is going to love this

2014-12-22 Thread Sean Farley
Jed Brown writes: > Sean Farley writes: >> The only way to do this, in my experience, is if the package manager has >> something like 'variants' (macports and homebrew have it, at least, I >> don't know about others): >> >> port install petsc +superlu +mumps +mpich +hdf5 +hypre ... etc. > > I th