libfast in: /PETSc3/petsc/petsc-dev/src/snes/impls/lsvi
lsvi.c: In function 'PetscErrorCode SNESLSVIComputeMeritFunction(_p_Vec*,
PetscScalar*)':
lsvi.c:137: error: no matching function for call to 'VecNormBegin(_p_Vec*,
NormType, PetscScalar*)'
/PETSc3/petsc/petsc-dev/include/petscvec.h:468:
Matt,
Nobody knows how you build stuff. Atleast mention the configure
command used so it can be reproduced and fixed..
Satish
On Thu, 19 Aug 2010, Matthew Knepley wrote:
libfast in: /PETSc3/petsc/petsc-dev/src/snes/impls/lsvi
lsvi.c: In function 'PetscErrorCode
On Thu, 19 Aug 2010 12:33:05 -0500 (CDT), Satish Balay balay at mcs.anl.gov
wrote:
Matt,
Nobody knows how you build stuff. Atleast mention the configure
command used so it can be reproduced and fixed..
Complex:
On Thu, 19 Aug 2010, Jed Brown wrote:
On Thu, 19 Aug 2010 12:33:05 -0500 (CDT), Satish Balay balay at mcs.anl.gov
wrote:
Matt,
Nobody knows how you build stuff. Atleast mention the configure
command used so it can be reproduced and fixed..
Complex:
We expect all our users to send complete logs - whenreporting
problems. we as developers should be able to include atleat minimal
realvent info in such e-mails - which is the configure command used.
I really need to start the twitter account for Satish: SatishSmackDown
Sean
--
On Thu, Aug 19, 2010 at 5:37 PM, Satish Balay balay at mcs.anl.gov wrote:
On Thu, 19 Aug 2010, Jed Brown wrote:
On Thu, 19 Aug 2010 12:33:05 -0500 (CDT), Satish Balay
balay at mcs.anl.gov wrote:
Matt,
Nobody knows how you build stuff. Atleast mention the configure
command used
On Thu, 19 Aug 2010, Matthew Knepley wrote:
On Thu, Aug 19, 2010 at 5:37 PM, Satish Balay balay at mcs.anl.gov wrote:
We expect all our users to send complete logs - whenreporting
problems. we as developers should be able to include atleat minimal
realvent info in such e-mails - which is
Shri - looks like merit should be PetscReal - not PetscComplex [pusing
a fix for this. If this is incorrect - you can revert my change]
That's correct...thanks.I am building petsc with complex right now to see if
there are any other changes needed.
Satish
Shri,
Since this is development code that only you are working on you can
protect its use by putting a
#requirespackage 'PETSC_USE_DVI'
in the makefile in that directory and if you register the method in
SNESRegisterAll() then protect it with
#if defined(PETSC_USE_DVI)
then define
I'm not sure whether DVI should have support for complex type since complex
variables with real upper and lower bounds don't make sense to me and i don't
know of any actual problems which have or need complex bounds.
- Barry Smith bsmith at mcs.anl.gov wrote:
Shri,
Since this
Then you can just require in that directory real numbers (and when you
register the method) so that make won't automatically try to build that stuff.
Barry
On Aug 19, 2010, at 6:12 PM, Shri wrote:
I'm not sure whether DVI should have support for complex type since complex
11 matches
Mail list logo
