Re: [petsc-dev] candidate branches for maint

2013-09-25 Thread Karl Rupp
Hi Satish, > Candidate for maint: refs/remotes/origin/karlrupp/feature-viennacl Mon Jun 10 16:44:57 2013 -0500 this should *not* go into maint, because GPU-stuff is disabled in the current release version. Best regards, Karli

[petsc-dev] Add new flag

2013-09-25 Thread Jose David Bermeol
Hi, in order to compile code with petsc and cpardiso I will need to compile with the flag -libiomp5, so when I call make test, the test fails because it is not compiling with this flag, how could I add this flag in a way that petsc take it into account. Thanks

Re: [petsc-dev] candidate branches for maint

2013-09-25 Thread Jed Brown
Satish Balay writes: > balay@asterix /home/balay/petsc.clone (next) > $ candidate-branches next maint > Candidate for maint: refs/remotes/origin/balay/fix-fenv.h-check-on-cygwin64 > Wed Sep 25 13:53:25 2013 -0500 > Candidate for maint: refs/remotes/origin/barry/fix-dgmres.c Mon Sep 16 > 16:38:1

Re: [petsc-dev] A couple of other notes from the Cygwin64 install

2013-09-25 Thread Aron Ahmadia
Also, I think we're using different build configurations, I don't produce a libpetsc.dll (that looks suspiciously like a libpetsc.so file with the wrong name). You should have a: lib/libpetsc.dll.a and cygpetsc.dll The first is the "import library" for the DLL, which contains the stubs for the

Re: [petsc-dev] A couple of other notes from the Cygwin64 install

2013-09-25 Thread Aron Ahmadia
What does cygcheck.exe have to say about it? A On Wed, Sep 25, 2013 at 6:05 PM, Satish Balay wrote: > On Wed, 25 Sep 2013, Satish Balay wrote: > > > On Wed, 25 Sep 2013, Aron Ahmadia wrote: > > > > > The Fortran test failed, I'm not going to bother looking into it. > > > > > > CMake is happily

Re: [petsc-dev] A couple of other notes from the Cygwin64 install

2013-09-25 Thread Satish Balay
On Wed, 25 Sep 2013, Satish Balay wrote: > On Wed, 25 Sep 2013, Aron Ahmadia wrote: > > > The Fortran test failed, I'm not going to bother looking into it. > > > > CMake is happily dumping the output library, cygpetsc.dll, in > > $PETSC_DIR/$PETSC_ARCH > > > > According to the wizards at Micros

Re: [petsc-dev] A couple of other notes from the Cygwin64 install

2013-09-25 Thread Satish Balay
On Wed, 25 Sep 2013, Aron Ahmadia wrote: > The Fortran test failed, I'm not going to bother looking into it. > > CMake is happily dumping the output library, cygpetsc.dll, in > $PETSC_DIR/$PETSC_ARCH > > According to the wizards at Microsoft/Cygwin, DLLs belong in bin/, so they > end up on the P

[petsc-dev] petsc4py + Cython + DL_IMPORT/__imp_ ugliness

2013-09-25 Thread Aron Ahmadia
Has anybody successfully built petsc4py on a Windows box? It looks like some of the Cython logic is not quite right. On Windows, Cython is trying to set the various functions in libpetsc4py.h for external DLL import. This wouldn't be a problem, except these functions are consumed *internally* by

Re: [petsc-dev] candidate branches for maint

2013-09-25 Thread Satish Balay
On Wed, 25 Sep 2013, Peter Brune wrote: > > Candidate for maint: refs/remotes/origin/prbrune/snes-jacobiancolormgfix > > Thu Aug 29 14:18:01 2013 -0500 > > > > > yup. This one should be in maint and master. Thanks. merged to maint now. Satish

Re: [petsc-dev] candidate branches for maint

2013-09-25 Thread Peter Brune
> Candidate for maint: refs/remotes/origin/prbrune/snes-jacobiancolormgfix > Thu Aug 29 14:18:01 2013 -0500 > > yup. This one should be in maint and master.

Re: [petsc-dev] candidate branches for maint

2013-09-25 Thread Satish Balay
On Wed, 25 Sep 2013, Matthew Knepley wrote: > On Wed, Sep 25, 2013 at 12:50 PM, Satish Balay wrote: > > > balay@asterix /home/balay/petsc.clone (next) > > $ candidate-branches master maint > > Candidate for maint: refs/remotes/origin/jed/attribute-deprecated-compat > > Sun Sep 1 18:35:59 2013 -0

Re: [petsc-dev] candidate branches for maint

2013-09-25 Thread Matthew Knepley
On Wed, Sep 25, 2013 at 12:50 PM, Satish Balay wrote: > balay@asterix /home/balay/petsc.clone (next) > $ candidate-branches master maint > Candidate for maint: refs/remotes/origin/jed/attribute-deprecated-compat > Sun Sep 1 18:35:59 2013 -0700 > > > Candidate for maint: refs/remotes/origin/jed/p

Re: [petsc-dev] Get/Create fixes and questions

2013-09-25 Thread Matthew Knepley
On Wed, Sep 25, 2013 at 11:40 AM, Barry Smith wrote: > > 1) >The following five routines create objects that the user needs to call > destroy on, the called object does not keep a reference > >MatGetFactor() >MatGetVecs() >KSPGetVecs() >PetscOptionsGetViewer() >DMDAGetRay(

Re: [petsc-dev] candidate branches for maint

2013-09-25 Thread Satish Balay
On Wed, 25 Sep 2013, Aron Ahmadia wrote: > Knepley's fix to dll detection is also not here: > > https://bitbucket.org/petsc/petsc/commits/branch/knepley/fix-configure-dll Looks like this one started off master - not maint. [if its destined for maint - then it should probably be cherry/picked to

Re: [petsc-dev] candidate branches for maint

2013-09-25 Thread Aron Ahmadia
Knepley's fix to dll detection is also not here: https://bitbucket.org/petsc/petsc/commits/branch/knepley/fix-configure-dll On Wed, Sep 25, 2013 at 3:50 PM, Satish Balay wrote: > balay@asterix /home/balay/petsc.clone (next) > $ candidate-branches master maint > Candidate for maint: refs/remote

[petsc-dev] candidate branches for maint

2013-09-25 Thread Satish Balay
balay@asterix /home/balay/petsc.clone (next) $ candidate-branches master maint Candidate for maint: refs/remotes/origin/jed/attribute-deprecated-compat Sun Sep 1 18:35:59 2013 -0700 Candidate for maint: refs/remotes/origin/jed/pcmg-residual-underscore Wed Jun 26 16:22:39 2013 -0500 Candidate fo

[petsc-dev] Get/Create fixes and questions

2013-09-25 Thread Barry Smith
1) The following five routines create objects that the user needs to call destroy on, the called object does not keep a reference MatGetFactor() MatGetVecs() KSPGetVecs() PetscOptionsGetViewer() DMDAGetRay() These should be changed to use Create 2) The routine DMDA

[petsc-dev] A couple of other notes from the Cygwin64 install

2013-09-25 Thread Aron Ahmadia
The Fortran test failed, I'm not going to bother looking into it. CMake is happily dumping the output library, cygpetsc.dll, in $PETSC_DIR/$PETSC_ARCH According to the wizards at Microsoft/Cygwin, DLLs belong in bin/, so they end up on the PATH when somebody tries to do an import. Cheers, Aron

Re: [petsc-dev] Disabling a header in configure based on a bad link?

2013-09-25 Thread Aron Ahmadia
Thanks Satish! A On Wed, Sep 25, 2013 at 12:34 PM, Satish Balay wrote: > Attached is the patch for this.. > > Satish > > On Wed, 25 Sep 2013, Satish Balay wrote: > > > perhaps the appropriate thing is to move the 'fenv.h' from the current > > location to this new test into config/BuildSystem/c

Re: [petsc-dev] Disabling a header in configure based on a bad link?

2013-09-25 Thread Satish Balay
Attached is the patch for this.. Satish On Wed, 25 Sep 2013, Satish Balay wrote: > perhaps the appropriate thing is to move the 'fenv.h' from the current > location to this new test into config/BuildSystem/config/headers.py > [i.e this code would add fenv.h header if the test is successful] > >

Re: [petsc-dev] Changing tests

2013-09-25 Thread Mark F. Adams
> >> SOR with multis dof? > > ex43 and snes ex19 do that in multigrid and there are other examples > that test more sizes of SOR. > In that case I can not think of anything that these test are testing other than gamg. So it sounds like you are saying that tests -- tutorial tests -- should not

[petsc-dev] Changing tests

2013-09-25 Thread Jed Brown
"Mark F. Adams" writes: >>> >> >> Fine, but why is the test a better test of PETSc by doing Richardson/SOR >> instead of Chebyshev/Jacobi? > > I don't know what better means but as I said it was intended to > exercise and demonstrate the recommended AMG parameters. Are those parameters not

Re: [petsc-dev] Disabling a header in configure based on a bad link?

2013-09-25 Thread Satish Balay
perhaps the appropriate thing is to move the 'fenv.h' from the current location to this new test into config/BuildSystem/config/headers.py [i.e this code would add fenv.h header if the test is successful] Satish On Wed, 25 Sep 2013, Aron Ahmadia wrote: > Hi folks, > > I'm working on a Cygwin64

Re: [petsc-dev] Disabling a header in configure based on a bad link?

2013-09-25 Thread Matthew Knepley
On Wed, Sep 25, 2013 at 7:32 AM, Aron Ahmadia wrote: > Hi folks, > > I'm working on a Cygwin64 port of PETSc and I have a question about doing > a specific disable in BuildSystem based on a failing link. > > The Cygwin folks provide an fenv.h implementation that (as far as I can > tell), is curre

[petsc-dev] Disabling a header in configure based on a bad link?

2013-09-25 Thread Aron Ahmadia
Hi folks, I'm working on a Cygwin64 port of PETSc and I have a question about doing a specific disable in BuildSystem based on a failing link. The Cygwin folks provide an fenv.h implementation that (as far as I can tell), is currently broken due to an undefined FE_DFL_ENV variable. My inclinatio