Re: [petsc-dev] buildsystem package dependencies
On Tue, Apr 5, 2011 at 11:20 AM, Satish Balay <[email protected]> wrote:
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
Right, but this MPE package is changing the MPI interface. All those other packages, like Hypre, depend on MPI. MPI depends on MPE, but the MPE module may modify the MPI lib to be '-lmpe -lmpi'. I do not see another way to do this. Matt
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 <[email protected]> wrote:
On 5 April 2011 12:54, Satish Balay <[email protected]> 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
-- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener
participants (1)
-
Matthew Knepley