[petsc-dev] dealing with MPIUNi

Lisandro Dalcin dalcinl at gmail.com
Fri Feb 26 15:32:38 CST 2010

On 26 February 2010 18:05, Barry Smith <bsmith at mcs.anl.gov> wrote:
>  Ok, it is still a mess as a special case but I don't see a way around it if
> we want users to be able to use the mpi.h and mpif.h directly. So it is back
> to adding the -Iinclude/mpiuni to the search directories. But there is never
> a libmpiuni.a

I still think that we should have an autogenerated "petscmpi.h" in
$PETSC_DIR/$PETSC_ARCH/include ... If third party code are using all
the niceties PETSc's Makefile infrastructure and moreover want to use
the PETSc-provided fake MPI without ever bothering for managing
include dirs, libraries and library dirs, I think it is reasonable to
ask these codes to change "mpi.h" -> "petscmpi.h" ... However, I
understand this could not work at all for Fortran 90 modules

Lisandro Dalcin
Centro Internacional de Métodos Computacionales en Ingeniería (CIMEC)
Instituto de Desarrollo Tecnológico para la Industria Química (INTEC)
Consejo Nacional de Investigaciones Científicas y Técnicas (CONICET)
PTLC - Güemes 3450, (3000) Santa Fe, Argentina
Tel/Fax: +54-(0)342-451.1594

More information about the petsc-dev mailing list