On Fri, Oct 10, 2008 at 6:29 PM, Deng, Ying wrote:
> Hi,
>
> I am seeing problems when trying to build petsc-dev code. My configure
> line is below, same as I successfully did for 2.3.2-p10. I tried with
> mkl 9 and mkl 10. Same errors. There are references to undefined
> symbols. Please share wit
Hi,
I am seeing problems when trying to build petsc-dev code. My configure
line is below, same as I successfully did for 2.3.2-p10. I tried with
mkl 9 and mkl 10. Same errors. There are references to undefined
symbols. Please share with me if you have any experience with the issue
or suggestion
Lisandro,
In the current model of initializations there are two submodels
1) no dynamic libraries (example Mat, others should be the same)
MatCreate() ALWAYS calls MatInitializePackage(). Inside
MatInitializePackage()
is a static variable indicating if initialization has take
In petsc4py, I've just implemented support for compose()/query() in my
base Object class. However, I wanted to implement query() in such a
way that 'dynamic_cast' (in the C++ sense, i.e, downcast) the composed
PETSc object and return to Python code an instance of the appropriate
Python type. Then,
That approach sounds fine. I think that initializing the COOKIEs was not
liked by some compilers. Ugh.
Matt
On Fri, Oct 10, 2008 at 1:31 PM, Lisandro Dalcin wrote:
> In petsc4py, I've just implemented support for compose()/query() in my
> base Object class. However, I wanted to implement quer
