[petsc-dev] PETSc always recompiles mpi4py petsc4py even when it does not have too

[Matthew Knepley]

On Sun, Oct 11, 2020 at 4:35 AM Barry Smith <bsmith at petsc.dev> wrote:

>
>
> On Oct 11, 2020, at 2:50 AM, Pierre Jolivet <pierre at joliv.et> wrote:
>
> This actually applies to all packages with builtafterpetsc = 1.
>
>
>   Yes, but now that petsc4py is part of the PETSc repository I would like
> to just alway have it turned on so now the rebuild is annoying.
>
> I think you want to do make libs instead of make all?
>
>
>   The problem is make libs is not parallel so much slower?
>

make -f ./gmakefile is not parallel?

  Matt


>   Barry
>
>
> Thanks,
> Pierre
>
> On 11 Oct 2020, at 9:36 AM, Barry Smith <bsmith at petsc.dev> wrote:
>
>
>   I change a single PETSc file and do make all that single file gets
> compiled but all of mpi4py and petsc4py get recompiled even though I have
> not changed any thing to affect them. No include files for example
>
>
> *** Building mpi4py ***
> *** Installing mpi4py ***
> =====================================
> To use mpi4py, add
> /Users/barrysmith/Src/petsc/arch-cleanup-dmd-domaindecomposition/lib to
> PYTHONPATH
> =====================================
> *** Building petsc4py ***
>
>
>
>

-- 
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

https://www.cse.buffalo.edu/~knepley/ <http://www.cse.buffalo.edu/~knepley/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20201011/d30535e2/attachment.html>