[petsc-dev] buildsystem package dependencies
Satish Balay
balay at mcs.anl.gov
Tue Apr 5 11:20:21 CDT 2011
Not sure I understand. If I say 'mpi depends on mpe' - then the link line is:
-lhypre -lmpi -lmpe
But thats incorrect usage - and not what I want.. The correct usage is:
-lhypre -lmpe -lmpi
The issue comes up with -llmpe - which traps MPI_xx functions - and does some
logging - and then calls MPI_xx functions from -lmpi. i.e usage is:
-lhypre -llmpe -lmpe -lmpi
Satish
On Tue, 5 Apr 2011, Matthew Knepley wrote:
> Yes, Lisandro is correct.
>
> Matt
>
> On Tue, Apr 5, 2011 at 11:05 AM, Lisandro Dalcin <dalcinl at gmail.com> wrote:
>
> > On 5 April 2011 12:54, Satish Balay <balay at mcs.anl.gov> wrote:
> > >
> > > Matt,
> > >
> > > Is it possible to specify package dependencies such that the following
> > happens:
> > >
> > > [all mpipackages like -lhypre] [-lmpe] -lmpi
> > >
> > > Currently I have:
> > > mpe: depends on mpi
> > > hypre: depends on mpi
> > >
> > > And configure can do:
> > > -lmpe -lhypre -lmpi
> > >
> > > But I want to say:
> > > mpe: depends on mpi, but before all other mpi packages.
> > >
> >
> > >From a library dependency POV, it is the other way around: MPI depends
> > on MPE, but the dependency is optional.
> >
> >
> >
> > --
> > Lisandro Dalcin
> > ---------------
> > CIMEC (INTEC/CONICET-UNL)
> > Predio CONICET-Santa Fe
> > Colectora RN 168 Km 472, Paraje El Pozo
> > 3000 Santa Fe, Argentina
> > Tel: +54-342-4511594 (ext 1011)
> > Tel/Fax: +54-342-4511169
> >
>
>
>
>
More information about the petsc-dev
mailing list