dolfin team mailing list archive

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

Jake Ostien wrote:
> Garth N. Wells wrote:
> > Quoting Jake Ostien <tostien@xxxxxxxxx>:
> >
> >  
> > > Hi,
> > >
> > > It appears that something is amiss when trying to compile DOLFIN with 
> > > petsc-2.3.3-p2, and --enable-petsc --enable-pydolfin.  When I try to 
> > > compile to demos I get the following...
> > >
> > > [jtostie@tostien demo]$ pwd
> > > /home/jtostie/downloads/src/fenics/dolfin/src/demo
> > > [jtostie@tostien demo]$ make
> > > Making all in la/eigensolver
> > > make[1]: Entering directory 
> > > `/home/jtostie/downloads/src/fenics/dolfin/src/demo/la/eigensolver'
> > > `pkg-config --variable=compiler dolfin` -o demo main.o `pkg-config 
> > > --cflags dolfin` `pkg-config --libs dolfin`
> > > /home/jtostie/builds/lib/libdolfin.so: undefined reference to 
> > > `PetscFListFind(int, _n_PetscFList*, char const*, void (**)())'
> > > collect2: ld returned 1 exit status
> > > make[1]: *** [demo] Error 1
> > > make[1]: Leaving directory 
> > > `/home/jtostie/downloads/src/fenics/dolfin/src/demo/la/eigensolver'
> > > make: *** [all-recursive] Error 1
> > >
> > > Has anyone else seen this?
> > >
> > >     
> >
> > Did you update SLEPc?
> >   
> No, and that solved the problem...thanks.
> >  
> >  
> > > Next up, I have two other references to gid and matrixmarket in 
> > > /src/pydolfin/dolfin_wrap.cpp that look like
> > > SWIG_Python_SetConstant(d, 
> > > "File_matrixmarket",SWIG_From_int(static_cast< int 
> > >  >(dolfin::File::matrixmarket)));
> > >
> > > I have just commented them out because apparently they don't exist 
> > > anymore in dolfin::File.h/cpp  (they almost certainly can be 
> > > removed).  Plus I haven't quite figured out hg yet beyond clone | 
> > > pull;update.
> > >
> > >     
> >
> > Just do
> >   touch src/pydolfin/dolfin.i
> >
> > and the 'make install'. dolfin_wrap.cpp is automatically generated by 
> > SWIG.
> >
> > Garth
> >
> >   
> That fixed the file type error, however I am still getting an error 
> related to HYPRE when I try and import the dolin module.  I have skirted 
> the HYPRE prblem when compiling the demos by manually tweaking the 
> dolfin.pc file, but I have not figured out how to do so  for pydolfin.  

DOLFIN shouldn't know anything about Hypre directly. What change do you 
need to make in dolfin.pc? What do you see when you do

  pkg-config --cflags dolfin

and

  pkg-config --libs dolfin

?

> Its not a big deal since I don't need pydolfin, but I thought it would 
> be interesting to get it working.  So the question is, is DOLFIN 
> officially dependent on HYPRE, 

No.

Garth

and if it is, shouldn't I be able to set
> the HYPRE path via the configure step?
> Thanks again,
> Jake
>
>
> > > -Jake
> > >
> > > _______________________________________________
> > > DOLFIN-dev mailing list
> > > DOLFIN-dev@xxxxxxxxxx
> > > http://www.fenics.org/mailman/listinfo/dolfin-dev
> > >
> > >     
> >
> >
> >