DOLFIN wrote:
> One or more new changesets pushed to the primary dolfin repository.
> A short summary of the last three changesets is included below.
>
> changeset:   3426:02122cbfce69c977def49f286c0b185f5c00d097
> tag:         tip
> user:        "Garth N. Wells <[EMAIL PROTECTED]>"
> date:        Sun Dec 02 00:24:15 2007 +0000
> files:       src/kernel/mesh/MPIManager.cpp 
> src/kernel/mesh/MPIMeshCommunicator.cpp src/kernel/mesh/Makefile.am 
> src/kernel/mesh/Makefile.in src/kernel/mesh/dolfin/MPIManager.h 
> src/kernel/mesh/dolfin/Makefile.am src/kernel/mesh/dolfin/Makefile.in 
> src/kernel/mesh/dolfin/dolfin_mesh.h src/sandbox/pmesh/main.cpp
> description:
> Small fixes for parallel mesh from Magnus.
>
>   


After downloading this, I get the following error when trying to run 
src/demo/pde/poisson/python/demo.py

    Traceback (most recent call last):
      File "demo.py", line 20, in ?
        from dolfin import *
      File
    
"/home/meg/src/dolfin/dolfin/local/lib/python2.4/site-packages/dolfin/__init__.py",
    line 4, in ?
        from assemble import *
      File
    
"/home/meg/src/dolfin/dolfin/local/lib/python2.4/site-packages/dolfin/assemble.py",
    line 17, in ?
        from dolfin import *
      File
    
"/home/meg/src/dolfin/dolfin/local/lib/python2.4/site-packages/dolfin/dolfin.py",
    line 7, in ?
        import _dolfin
    ImportError:
    
/home/meg/src/dolfin/dolfin/local/lib/python2.4/site-packages/dolfin/_dolfin.so:
    undefined symbol: _ZN6dolfin19MPIMeshCommunicator10processNumEv


Similarly, the cpp demo compiles, but gives the following error when run

    terminate called after throwing an instance of 'std::runtime_error'
      what():  *** Error: Cannot broadcast meshes without MPI.
    Aborted


Anyone else observed this?

-- 
Marie E. Rognes
Ph.D Fellow, 
Centre of Mathematics for Applications, 
University of Oslo
http://folk.uio.no/meg

_______________________________________________
DOLFIN-dev mailing list
[email protected]
http://www.fenics.org/mailman/listinfo/dolfin-dev

Reply via email to