[petsc-dev] [petsc-maint] Updating PETSc to support Elemental 0.80

Jack Poulson jack.poulson at gmail.com
Mon Jun 24 14:21:11 CDT 2013


On Mon, Jun 24, 2013 at 11:56 AM, Satish Balay <balay at mcs.anl.gov> wrote:

>
> > If I am to have Clique build on top of pkg-metis and pkg-parmetis, I will
> > need to modify them to install enough header files so that it can make
> use
> > of metislib.h and parmetislib.h.
>
> So clique requires additional include files? I supporse these are
> private include files from metis/parmetis..
>
>
Yes, I wanted nodal bisection routines, and (par)metis only provides a
restrictive nested dissection routine. I therefore implemented sequential
and parallel versions using metis and parmetis's internal APIs. See
https://github.com/poulson/Clique/blob/master/src/metis/Bisect.c
and
https://github.com/poulson/Clique/blob/master/src/parmetis/ParallelBisect.c


> >  I'll try to propose a patch over the next
> > few days and include the 'include_directories(headers)' and replace the
> > strange 'include(FindMpi); if(NOT MPI_FOUND)' statements with guarded
> > 'find_package(MPI); if(NOT MPI_C_FOUND)' statements.
>
>
> Looks like that piece of code is from upstream. It has the comment:
> >>
> # GK commented this out as it seems to be creating problems
> <<
>
>
Agreed. But the reason it is commented out might be because of incorrect
usage of the CMake script. From the point of view of someone just trying to
build parmetis, it helps to have it there (whether optional or not).

Jack
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130624/37ebfe8d/attachment.html>


More information about the petsc-dev mailing list