On Sep 13, 2011, at 4:14, Johannes Ring <email address hidden> wrote:
> I'm still getting the same error with the latest dolfin-dev and it seems
> that boost_shared_ptr.i is already included in
> dolfin/swig/shared_ptr_classes.i. Any idea what I should do?
>
> --
> You received this bug notification because you are a member of DOLFIN
> Core Team, which is subscribed to DOLFIN.
> https://bugs.launchpad.net/bugs/799513
>
> Title:
> Snow Leopard demos fail with Swig 2.0.4
>
> Status in DOLFIN:
> Confirmed
>
> Bug description:
> I'm on Snow Leopard, and build FEniCS with dorsal-0.8.2. Dependencies
> installed with macports, on a fresh OS X install.
>
> Everything I run results in the error below. Other people who have had
> this problem seemed to resolved it by running instant-clean, which
> appears to run successfully, but I still get the same error.
>
> rob@cosmo python $ python demo.py
> Calling FFC just-in-time (JIT) compiler, this may take some time.
> Traceback (most recent call last):
> File "demo.py", line 22, in <module>
> V = VectorFunctionSpace(mesh, "CG", 2)
> File "/Users/rob/Development/FEniCS/lib/python2.7/site-packages/dolfin/function/functionspace.py", line 321, in __init__
> restriction=restriction)]
> File "/Users/rob/Development/FEniCS/lib/python2.7/site-packages/dolfin/function/functionspace.py", line 237, in __init__
> FunctionSpaceBase.__init__(self, mesh, element)
> File "/Users/rob/Development/FEniCS/lib/python2.7/site-packages/dolfin/function/functionspace.py", line 47, in __init__
> self._dolfin_element = cpp.FiniteElement(ufc_element)
> File "/Users/rob/Development/FEniCS/lib/python2.7/site-packages/dolfin/cpp.py", line 14561, in __init__
> _cpp.FiniteElement_swiginit(self,_cpp.new_FiniteElement(*args))
> TypeError: in method 'new_FiniteElement', argument 1 of type 'boost::shared_ptr< ufc::finite_element const >'
>
>
> Any advice is much appreciated!
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/dolfin/+bug/799513/+subscriptions
Have you tried the development version of SWIG?
Johan
On Sep 13, 2011, at 4:14, Johannes Ring <email address hidden> wrote:
> I'm still getting the same error with the latest dolfin-dev and it seems swig/shared_ ptr_classes. i. Any idea what I should do? /bugs.launchpad .net/bugs/ 799513 pace(mesh, "CG", 2) rob/Development /FEniCS/ lib/python2. 7/site- packages/ dolfin/ function/ functionspace. py", line 321, in __init__ restriction) ] rob/Development /FEniCS/ lib/python2. 7/site- packages/ dolfin/ function/ functionspace. py", line 237, in __init__ se.__init_ _(self, mesh, element) rob/Development /FEniCS/ lib/python2. 7/site- packages/ dolfin/ function/ functionspace. py", line 47, in __init__ element = cpp.FiniteEleme nt(ufc_ element) rob/Development /FEniCS/ lib/python2. 7/site- packages/ dolfin/ cpp.py" , line 14561, in __init__ ent_swiginit( self,_cpp. new_FiniteEleme nt(*args) ) ent', argument 1 of type 'boost::shared_ptr< ufc::finite_element const >' /bugs.launchpad .net/dolfin/ +bug/799513/ +subscriptions
> that boost_shared_ptr.i is already included in
> dolfin/
>
> --
> You received this bug notification because you are a member of DOLFIN
> Core Team, which is subscribed to DOLFIN.
> https:/
>
> Title:
> Snow Leopard demos fail with Swig 2.0.4
>
> Status in DOLFIN:
> Confirmed
>
> Bug description:
> I'm on Snow Leopard, and build FEniCS with dorsal-0.8.2. Dependencies
> installed with macports, on a fresh OS X install.
>
> Everything I run results in the error below. Other people who have had
> this problem seemed to resolved it by running instant-clean, which
> appears to run successfully, but I still get the same error.
>
> rob@cosmo python $ python demo.py
> Calling FFC just-in-time (JIT) compiler, this may take some time.
> Traceback (most recent call last):
> File "demo.py", line 22, in <module>
> V = VectorFunctionS
> File "/Users/
> restriction=
> File "/Users/
> FunctionSpaceBa
> File "/Users/
> self._dolfin_
> File "/Users/
> _cpp.FiniteElem
> TypeError: in method 'new_FiniteElem
>
>
> Any advice is much appreciated!
>
> To manage notifications about this bug go to:
> https:/