Re: [petsc-dev] IMPORTANT PETSc repository changed from Bucketbit to GitLab

2019-08-22 Thread Balay, Satish via petsc-dev
On Mon, 19 Aug 2019, Smith, Barry F. via petsc-dev wrote: > > >PETSc folks. > > This announcement is for people who access PETSc from the BitBucket > repository or post issues or have other activities with the Bitbucket > repository > >We have changed the location of the PETSc

Re: [petsc-dev] Sequential external packages and MPI

2019-08-22 Thread Balay, Satish via petsc-dev
On Thu, 22 Aug 2019, Pierre Jolivet via petsc-dev wrote: > > > > On 22 Aug 2019, at 7:42 AM, Balay, Satish wrote: > > > > On Thu, 22 Aug 2019, Pierre Jolivet via petsc-dev wrote: > > > >> Hello, > >> PETSc is linking “sequential” libraries with MPI libraries. > >> $ otool -L libmetis.dylib >

Re: [petsc-dev] Sequential external packages and MPI

2019-08-22 Thread Balay, Satish via petsc-dev
But they pick default compilers [prefer gcc] - that might not be compatible with MPI compilers. This is preferred because - esp in cross-compile env - these tools are run on the front-end node - and PETSc applications are run on the back-end [compute] nodes. Also we have --download-sowing-cc=

Re: [petsc-dev] Sequential external packages and MPI

2019-08-22 Thread Balay, Satish via petsc-dev
On Thu, 22 Aug 2019, Pierre Jolivet via petsc-dev wrote: > > > > On 22 Aug 2019, at 7:42 AM, Balay, Satish wrote: > > > > On Thu, 22 Aug 2019, Pierre Jolivet via petsc-dev wrote: > > > >> Hello, > >> PETSc is linking “sequential” libraries with MPI libraries. > >> $ otool -L libmetis.dylib >

Re: [petsc-dev] Sequential external packages and MPI

2019-08-22 Thread Jed Brown via petsc-dev
"Smith, Barry F. via petsc-dev" writes: >> Our Metis wrapper is marked as a sequential one, but since you are linking >> libmetis with MPI, this is problematic for some configurations. > > What is your work flow? Are you using --prefix to compile particular > combinations of external

Re: [petsc-dev] Sequential external packages and MPI

2019-08-22 Thread Pierre Jolivet via petsc-dev
OK, thanks to you both for your comments. I’ll try to figure something out. Pierre > On 22 Aug 2019, at 8:19 AM, Smith, Barry F. wrote: > > > cmake, make, sowing and utilities that are not libraries that go into the > overall simulation are not compiled with mpicxx etc. > >> On Aug 22,

Re: [petsc-dev] Sequential external packages and MPI

2019-08-22 Thread Smith, Barry F. via petsc-dev
cmake, make, sowing and utilities that are not libraries that go into the overall simulation are not compiled with mpicxx etc. > On Aug 22, 2019, at 1:03 AM, Pierre Jolivet via petsc-dev > wrote: > > > >> On 22 Aug 2019, at 7:42 AM, Balay, Satish wrote: >> >> On Thu, 22 Aug 2019,

Re: [petsc-dev] Sequential external packages and MPI

2019-08-22 Thread Smith, Barry F. via petsc-dev
> On Aug 22, 2019, at 12:31 AM, Pierre Jolivet via petsc-dev > wrote: > > Hello, > PETSc is linking “sequential” libraries with MPI libraries. > $ otool -L libmetis.dylib > /usr/local/opt/mpich/lib/libmpi.12.dylib (compatibility version 14.0.0, > current version 14.7.0) > $ otool -L

Re: [petsc-dev] Sequential external packages and MPI

2019-08-22 Thread Pierre Jolivet via petsc-dev
> On 22 Aug 2019, at 7:42 AM, Balay, Satish wrote: > > On Thu, 22 Aug 2019, Pierre Jolivet via petsc-dev wrote: > >> Hello, >> PETSc is linking “sequential” libraries with MPI libraries. >> $ otool -L libmetis.dylib >> /usr/local/opt/mpich/lib/libmpi.12.dylib (compatibility version