On 26 Mar 2014, at 08:55, Geoff Oxberry <[email protected]> wrote:

> I have a similar error to a user who wrote in 2014-03-03 (see 
> https://www.mail-archive.com/[email protected]/msg00366.html):
> 
> Traceback (most recent call last):
>   File "demo_poisson.py", line 41, in <module>
>     V = FunctionSpace(mesh, "Lagrange", 1)
>   File 
> "~/FEniCS/lib/python2.7/dist-packages/dolfin/functions/functionspace.py", 
> line 403, in __init__
>     FunctionSpaceBase.__init__(self, mesh, element, constrained_domain)
>   File "
> ~/FEniCS/lib/python2.7/dist-packages/dolfin/functions/functionspace.py", 
> 
> line 84, in __init__
>     ufc_element, ufc_dofmap = jit(self._ufl_element)
>   File "
> ~/FEniCS/lib/python2.7/dist-packages/dolfin/compilemodules/jit.py", line 
> 
> 60, in mpi_jit
>     return local_jit(*args, **kwargs)
>   File "
> ~/FEniCS/lib/python2.7/dist-packages/dolfin/compilemodules/jit.py", line 
> 
> 122, in jit
>     return jit_compile(form, parameters=p, common_cell=common_cell)
> TypeError: jit() got an unexpected keyword argument 'common_cell'
> 
> 
> In the same thread, Anders Logg suggested updating DOLFIN, UFL, and FFC. I 
> installed everything through Dorsal; to my knowledge, each package is at the 
> most recent stable version. If you let me know which files to send, I can 
> send build logs.
> 
> I've also tried using Dorsal to build the development versions of these 
> packages. On OS X with Homebrew and LLVM 3.3, there seems to be an issue with 
> the development version of FFC; clang++ throws a number of errors related to 
> std::shared_ptr (in SWIG-generated interfaces) that have to do with the 
> version of libstdc++ clang++ is using. If I compile and link with libc++ 
> instead, those problems go away, but linking errors occur (with Boost; 
> rebuilding Boost with libc++ does not seem to work either).
> 
> Are there other ways to resolve this problem while still building with 
> Homebrew?
> 

I don’t think any developers use (or have access to) OS X 10.8, so it all be 
hard for us to fix. I build the FEniCS dev versions on OSX 10.9 with Xcode 5.1 
without problems. I install via Homebrew all the dependencies that are 
available in Homebrew, except PETSc which I choose to build myself.

Garth 


> Cheers,
> 
> Geoff
> _______________________________________________
> fenics-support mailing list
> [email protected]
> http://fenicsproject.org/mailman/listinfo/fenics-support

_______________________________________________
fenics-support mailing list
[email protected]
http://fenicsproject.org/mailman/listinfo/fenics-support

Reply via email to