dolfin team mailing list archive

["Garth N. Wells" <g.n.wells@xxxxxxxxxx>]

Anders Logg wrote:
> On Thu, Aug 10, 2006 at 12:51:40PM +0200, Garth N. Wells wrote:
> > Anders Logg wrote:
> > > Strange. I had the same problem and then the make install at the top
> > > level solved the problem.
> > >
> > > Do you have MAIN__ in your _dolfin.so? What do you get with
> > >
> > >     nm local/lib/python2.4/site-packages/dolfin/_dolfin.so | grep MAIN
> > Yes.
> >
> > $ nm local/lib/python2.4/site-packages/dolfin/_dolfin.so | grep MAIN
> >           U MAIN__
>
> I don't have this symbol. I did a search on this and it seems to be a
> Fortran thing (don't know why it should show up).

It's probably from PETSc which does have some Fortran code if a Fortran 
compiler is detected.



> Does it help if you add the following somewhere, to for example
> SettingsGlue.cpp in src/pydolfin?
>
> int MAIN__() { return(0); }
>
> And then regenerate the SWIG interface + make install.

Doesn't help. I'll try some other things.

Garth

> /Anders
>
> > Garth
> >
> > > Anyone else experiencing this?
> > >
> > > /Anders
> > >
> > >
> > > On Thu, Aug 10, 2006 at 12:11:57PM +0200, Garth N. Wells wrote:
> > > > Still not having any luck. After regenerating the SWIG interface and 
> > > > running make install from the top directory, I still get an error.
> > > >
> > > > Garth
> > > >
> > > >  >>> from dolfin import *
> > > > Importing DOLFIN
> > > > Traceback (most recent call last):
> > > >    File "<stdin>", line 1, in ?
> > > >    File 
> > > > "/tmp/dolfin/local/lib/python2.4/site-packages/dolfin/__init__.py", line 
> > > > 5, in ?
> > > >      from dolfin import *
> > > >    File 
> > > > "/tmp/dolfin/local/lib/python2.4/site-packages/dolfin/dolfin.py", line 
> > > > 4, in ?
> > > >      import _dolfin
> > > > ImportError: 
> > > > /tmp/dolfin/local/lib/python2.4/site-packages/dolfin/_dolfin.so: 
> > > > undefined symbol: MAIN__
> > > >
> > > >
> > > > Anders Logg wrote:
> > > > > On Thu, Aug 10, 2006 at 11:17:24AM +0200, Garth N. Wells wrote:
> > > > > > Anders Logg wrote:
> > > > > > > Does it help if you regenerate the SWIG interface?
> > > > > > >
> > > > > > > Go to src/pydolfin and do a touch dolfin.i followed by a make install.
> > > > > > Tried this, and now I get the below error. I've set the path,
> > > > > >
> > > > > >    >env | grep PYTHON
> > > > > >    PYTHONPATH=/tmp/dolfin/local/lib/python2.4/site-packages:
> > > > > >
> > > > > > Garth
> > > > > >
> > > > > >  >>> from dolfin import *
> > > > > > Traceback (most recent call last):
> > > > > >    File "<stdin>", line 1, in ?
> > > > > >    File "dolfin.py", line 4, in ?
> > > > > >      import _dolfin
> > > > > > ImportError: No module named _dolfin
> > > > > I got the same error myself. But a 'make install' in the top level
> > > > > directory should help.
> > > > >
> > > > > /Anders
> > > > >
> > > > >
> > > > > > > It could be that the SWIG interface has been generated by a different
> > > > > > > version of SWIG. I think Johan is the last person that regenerated the
> > > > > > > interface. I'm running SWIG 1.3.27 myself.
> > > > > > >
> > > > > > > /Anders
> > > > > > >
> > > > > > >
> > > > > > > On Thu, Aug 10, 2006 at 10:46:21AM +0200, Garth N. Wells wrote:
> > > > > > > > Anders Logg wrote:
> > > > > > > > > No problem for me. How do I know umfpack is enabled? I have
> > > > > > > > > libumfpack4 and libumfpack4-dev installed.
> > > > > > > > Same. I just cloned a new version of DOLFIN, and I still have the same 
> > > > > > > > error message.
> > > > > > > >
> > > > > > > > I removed umfpack, and now I get the below error message.
> > > > > > > >
> > > > > > > > Garth
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >  >>> from dolfin import *
> > > > > > > > Importing DOLFIN
> > > > > > > > Traceback (most recent call last):
> > > > > > > >    File "<stdin>", line 1, in ?
> > > > > > > >    File 
> > > > > > > > "/tmp/dolfin/local/lib/python2.4/site-packages/dolfin/__init__.py", line 
> > > > > > > > 5, in ?
> > > > > > > >      from dolfin import *
> > > > > > > >    File 
> > > > > > > > "/tmp/dolfin/local/lib/python2.4/site-packages/dolfin/dolfin.py", line 
> > > > > > > > 4, in ?
> > > > > > > >      import _dolfin
> > > > > > > > ImportError: 
> > > > > > > > /tmp/dolfin/local/lib/python2.4/site-packages/dolfin/_dolfin.so: 
> > > > > > > > undefined symbol: MAIN__
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > > /Anders
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Thu, Aug 10, 2006 at 08:56:25AM +0200, Anders Logg wrote:
> > > > > > > > > > Will check if I get the same error with umfpack (have not installed it
> > > > > > > > > > before).
> > > > > > > > > >
> > > > > > > > > > /Anders
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On Wed, Aug 09, 2006 at 03:33:34PM +0200, Garth N. Wells wrote:
> > > > > > > > > > > I'm trying out pyDOLFIN, but I'm getting an error that appears to be 
> > > > > > > > > > > related to UMFPACK. Any ideas?
> > > > > > > > > > >
> > > > > > > > > > > Garth
> > > > > > > > > > >
> > > > > > > > > > >  >>> from dolfin import *
> > > > > > > > > > > Importing DOLFIN
> > > > > > > > > > > Traceback (most recent call last):
> > > > > > > > > > >    File "<stdin>", line 1, in ?
> > > > > > > > > > >    File 
> > > > > > > > > > > "/usr/local/garth/fenics/dolfin/working/dolfin_petsc/local/lib/python2.4/site-packages/dolfin/__init__.py", 
> > > > > > > > > > > line 5, in ?
> > > > > > > > > > >      from dolfin import *
> > > > > > > > > > >    File 
> > > > > > > > > > > "/usr/local/garth/fenics/dolfin/working/dolfin_petsc/local/lib/python2.4/site-packages/dolfin/dolfin.py", 
> > > > > > > > > > > line 4, in ?
> > > > > > > > > > >      import _dolfin
> > > > > > > > > > > ImportError: 
> > > > > > > > > > > /usr/local/garth/fenics/dolfin/working/dolfin_petsc/local/lib/libdolfin.so.0: 
> > > > > > > > > > > undefined symbol: umfpack_di_transpose
> > > > > > > > > > > _______________________________________________
> > > > > > > > > > > DOLFIN-dev mailing list
> > > > > > > > > > > DOLFIN-dev@xxxxxxxxxx
> > > > > > > > > > > http://www.fenics.org/mailman/listinfo/dolfin-dev
> > > > > > > > > > _______________________________________________
> > > > > > > > > > DOLFIN-dev mailing list
> > > > > > > > > > DOLFIN-dev@xxxxxxxxxx
> > > > > > > > > > http://www.fenics.org/mailman/listinfo/dolfin-dev
> > > > > > > _______________________________________________
> > > > > > > DOLFIN-dev mailing list
> > > > > > > DOLFIN-dev@xxxxxxxxxx
> > > > > > > http://www.fenics.org/mailman/listinfo/dolfin-dev
> > > > > > _______________________________________________
> > > > > > DOLFIN-dev mailing list
> > > > > > DOLFIN-dev@xxxxxxxxxx
> > > > > > http://www.fenics.org/mailman/listinfo/dolfin-dev
> > > > > _______________________________________________
> > > > > DOLFIN-dev mailing list
> > > > > DOLFIN-dev@xxxxxxxxxx
> > > > > http://www.fenics.org/mailman/listinfo/dolfin-dev
> > > > _______________________________________________
> > > > DOLFIN-dev mailing list
> > > > DOLFIN-dev@xxxxxxxxxx
> > > > http://www.fenics.org/mailman/listinfo/dolfin-dev
> > > _______________________________________________
> > > DOLFIN-dev mailing list
> > > DOLFIN-dev@xxxxxxxxxx
> > > http://www.fenics.org/mailman/listinfo/dolfin-dev
> > _______________________________________________
> > DOLFIN-dev mailing list
> > DOLFIN-dev@xxxxxxxxxx
> > http://www.fenics.org/mailman/listinfo/dolfin-dev
> _______________________________________________
> DOLFIN-dev mailing list
> DOLFIN-dev@xxxxxxxxxx
> http://www.fenics.org/mailman/listinfo/dolfin-dev