dolfin team mailing list archive

[Anders Logg <logg@xxxxxxxxx>]

Great! When you get the PETSc and DOLFIN packages working, I can
arrange to put them on fenics.org if you agree to maintain the
packages (update for new releases) and if we can redirect any
questions about the packages to you.

How difficult would it be to get the packages into Debian?

/Anders

On Tue, Jul 05, 2005 at 04:13:10PM -0400, Faheem Mitha wrote:
> 
> 
> On Mon, 4 Jul 2005, Anders Logg wrote:
> 
> >On Mon, Jul 04, 2005 at 11:44:47PM -0400, Faheem Mitha wrote:
> >>
> >>
> >>On Mon, 4 Jul 2005, Faheem Mitha wrote:
> >>
> >>>On Mon, 4 Jul 2005, Anders Logg wrote:
> >>
> >>>>Look through the PETSc makefile and
> >>>>see if you find the target "getincludedirs".
> >>>>
> >>>>In my petsc-2.2.1/makefile:
> >>>>
> >>>>  include ${PETSC_DIR}/bmake/common/base
> >>>
> >>>Yes, it's there.
> >>
> >>Just to clarify, this is in the sources, but not in the installed library.
> >>You weren't expecting it to be there, were you?
> >
> >Yes, I was. DOLFIN needs to figure out where to find PETSc and it then
> >uses the getincludedirs flag with make to get the correct flags.
> >
> >If possible, I would rather do a 'make install' in PETSc like with any
> >other library (without needing to set PETSC_DIR to something special),
> >but then I don't know how to get compiler flags and link libraries
> >correctly. It would be nice to have a petsc-config script (like
> >gtk-config, xml2-config, dolfin-config, etc) that spits out the flags.
> >
> >If someone has any better suggestions for how to compile against PETSc,
> >please send me a patch. Only the the PETSc specific part in
> >configure.ac for DOLFIN would have to change.  (If you edit this file,
> >then run ./scripts/preconfigure and then ./configure.)
> 
> Hi,
> 
> I put the makefile in at the top level, under the top 
> level of /usr/lib/petsc-2.2.1 (this is the output of 'make install').
> 
> Now DOLFIN compiles correctly.
> 
> I'm going to go ahead and change the Debian package so that this makefile 
> is added to the top level of the installed library directory.
> 
> Then I'll go ahead and build a DOLFIN package, which should be 
> straightforward.
> 
> I realise that this is just a temporary fix, but we need working packages 
> ASAP, and it is a start.
> 
> I hope the problems with DOLFIN compilation against a PETSc installation 
> can be resolved.
> 
> I'll be back in touch once I've done the above.
> 
> Thanks.                                                          Faheem.
> 
> _______________________________________________
> DOLFIN-dev mailing list
> DOLFIN-dev@xxxxxxxxxx
> http://www.fenics.org/cgi-bin/mailman/listinfo/dolfin-dev
> 

-- 
Anders Logg
Research Assistant Professor
Toyota Technological Institute at Chicago
http://www.tti-c.org/logg/