To add more confusion:
I thought it might be because I was using swig 2.12, so I upgraded to 3.0.0
and remake'd dolfin. It complained that ufc was compiled with a different
swig version so I rebuilt ffc too (without cleaning the directory or
anything first). Ran make on dolfin again and it compiled!

Now when I try to import dolfin in python it says it can't import the
module la.  I thought that might be because I was sloppy about not cleaning
fcc before rebuilding it, so I deleted the whole fcc folder, cloned it and
rebuilt everything and sure enough dolfin pops out with the same error
message again...




On Wed, Apr 9, 2014 at 10:54 AM, Mike Welland <[email protected]> wrote:

> Hi,
>
> I am trying to compile on a cluster using gcc 4.8.1. When building dolfin
> (everything else should be in place) I get to 95% and it crashes:
>
> [ 95%] Building CXX object
> dolfin/CMakeFiles/dolfin.dir/refinement/RivaraRefinement.cpp.o
> [ 95%] Building CXX object
> dolfin/CMakeFiles/dolfin.dir/refinement/UniformMeshRefinement.cpp.o
> [ 95%] Building CXX object
> dolfin/CMakeFiles/dolfin.dir/refinement/refine.cpp.o
> Linking CXX shared library libdolfin.so
> [ 95%] Built target dolfin
> Scanning dependencies of target copy_swig_files
> [ 95%] Built target copy_swig_files
> make[2]: *** No rule to make target `copy_swig_files', needed by
> `dolfin/swig/modules/mesh/modulePYTHON_wrap.cxx'.  Stop.
> make[1]: *** [dolfin/swig/modules/mesh/CMakeFiles/_mesh.dir/all] Error 2
> make: *** [all] Error 2
>
> I am building from a new directory /dolfin/build so as to avoid a similar
> problem. There is another swig installed in /usr/bin/swig but it is old
> (1.5.x), so I built 2.12 in my home directory along with much of the
> others. I went through the CMakeCashe.txt to ensure everything is pointing
> to the right places and it is, and dolfin, fcc, instant, fiat and ufl were
> all cloned in the last 24 hours.
>
> Any help would be very much appreciated!
> Mike
>
> _______________________________________________
> 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