← Back to team overview

dolfin team mailing list archive

Re: pydolfin doesn't work

 

On Fri, Dec 19, 2008 at 11:55:16AM -0700, Bartosz Sawicki wrote:
> In current version of dolfin (freshly recompiled), pydolfin doesn't work 
> at all.
> This ipython error log should be enough to find the problem.
> 
> In [19]: import dolfin
> ---------------------------------------------------------------------------
> ImportError                               Traceback (most recent call last)
> 
> /home/sawickib/fenics/test/<ipython console> in <module>()
> 
> /home/sawickib/dolfin/local/lib/python2.5/site-packages/dolfin/__init__.py
> in <module>()
>       14 # Imports from Python code
>       15 from constants import *
> ---> 16 from assemble import *
>       17 from constant import *
>       18 from specialfunctions import *
> 
> /home/sawickib/dolfin/local/lib/python2.5/site-packages/dolfin/assemble.py
> in <module>()
>       23 # Import FFC and SWIG-generated extension module (DOLFIN C++)
>       24 import ffc
> ---> 25 import cpp
>       26
>       27 # Local imports
> 
> /home/sawickib/dolfin/local/lib/python2.5/site-packages/dolfin/cpp.py
> in <module>()
>        5 # This file is compatible with both classic and new-style classes.
>        6
> ----> 7 import _cpp
>        8 import new
>        9 new_instancemethod = new.instancemethod
> 
> ImportError: 
> /home/sawickib/dolfin/local/lib/python2.5/site-packages/dolfin/_cpp.so:
> undefined symbol: _ZNK6dolfin8Function4evalEPdRKNS_4DataE
> 
> 
> BArtek

No problems here. Are you sure you have pulled the latest sources?

The missing symbol refers to (checked with c++filt):

  dolfin::Function::eval(double*, dolfin::Data const&) const

and it's there in Function.cpp.

-- 
Anders

Attachment: signature.asc
Description: Digital signature


Follow ups

References