[petsc-dev] failure of new parallel configure

Matthew Knepley knepley at gmail.com
Tue Mar 3 14:45:07 CST 2015


On Tue, Mar 3, 2015 at 2:37 PM, Satish Balay <balay at mcs.anl.gov> wrote:

> On Tue, 3 Mar 2015, Matthew Knepley wrote:
>
> > Okay, I pushed the fixes for the MPI stuff. Lets see how next does now.
>
> I see the following issue with 'make all'
>

Is that a configure problem?

Also note that I removed a cycle in the configure graph. mpi4py depends on
PETSc.Configure, but Configure also depended on it which was crazy.

  Thanks,

     Matt


> Satish
>
> ----------
>
>      CLINKER /home/balay/petsc/arch-linux2-c-debug/lib/libpetsc.so.3.05.3
> gmake[2]: Leaving directory '/home/balay/petsc'
> =========================================
> gmake[1]: *** No rule to make target 'mpi4py-build', needed by
> 'all-gnumake-local'.  Stop.
> gmake[1]: Leaving directory '/home/balay/petsc'
> Now to check if the libraries are working do:
> make PETSC_DIR=/home/balay/petsc PETSC_ARCH=arch-linux2-c-debug test
> =========================================
>



-- 
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20150303/26f1b23e/attachment.html>


More information about the petsc-dev mailing list