dolfin team mailing list archive

[Anders Logg <logg@xxxxxxxxx>]

On Tue, Oct 25, 2005 at 01:51:36PM -0500, Barry Smith wrote:
> 
>   Due to a request from the dolfin folks; we have moved
>  src/ksp/pc/pcimpl.h to include/private/pcimpl.h This will
> be its new permanent location. 

We will use it once we move to the new version of PETSc. (And thank
you so much for making pcimpl.h accessible!)

>From what I understand, the next version of PETSc is expected to be
ready in December (?) so we will probably hold off until then.

It would be pretty simple to add a test to configure.ac and then some
#ifdefs in the right places to make DOLFIN compile with both versions
of PETSc. (We had this before to choose between different versions of
PETSc but we removed it since no one had time to maintain it.)

I wouldn't mind a patch to handle this.

/Anders

>   The version information is in include/petscversion.h so you
> can test against those. Note that PETSC_VERSION_RELEASE 1 indicates
> it is the released version while 0 indicates it is the 
> development version (strange choice of variable name?).
> 
>   Barry
> 
> On Tue, 25 Oct 2005, [iso-8859-1] Åsmund Ødegård wrote:
> 
> > Hi folks,
> > 
> > I try to compile dolfin against the version of petsc in darcs (i.e. at
> > http://www-unix.mcs.anl.gov/petsc/petsc-as/snapshots/petsc-dev-darcs).
> > 
> > A few files in dolfin (src/kernel/la/GMRES.cpp, and
> > /src/kernel/la/Preconditioner.cpp so far) reference src/ksp/pc/pcimpl.h,
> > which is kind of correct on petsc2.3.0 but incorrect on petsc-dev, where the
> > file is located in include/private/pcimpl.h.
> > 
> > Is this change intentionally?
> > 
> > Do we have some easy way of checking which version of petsc I am compiling
> > against?
> > 
> > I should probably just use petsc2.3.0, but there was some problems during
> > compile... ;-)
> > 
> > take care,
> > 
> > 

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