> On Feb 2, 2016, at 7:00 PM, Jed Brown <[email protected]> wrote:
> 
> Satish Balay <[email protected]> writes:
>> Or you can copy the whole '$PETSC_ARCH/externalpackages' dir over to
>> this other machine [and place in the same location - for any
>> PETSC_ARCH you plan to use..]
> 
> This sounds unreliable.

  In what way? 

>  We used to have a unified externalpackages
> directory, but made it per-PETSC_ARCH partly to avoid dirty source trees
> causing incorrect builds (and so that configure could run in parallel
> for different PETSC_ARCH).

Reply via email to