[petsc-dev] --known-mpi-shared-library and --with-batch annoyance

Lisandro Dalcin dalcinl at gmail.com
Thu Apr 21 17:02:17 CDT 2016

On 21 April 2016 at 20:08, Matthew Knepley <knepley at gmail.com> wrote:
> PETSc used to have multiple shared libraries, and its still possible. If you
> link MPI statically into multiple shared libraries,
> you duplicate symbols like isInitialized. This messes up tons of things in
> MPI.
>> 2) Is there any way to get rid of this flag or will there be cases were
>> configure goes through with success and accepts using shared libraries but
>> then the build fails with unable to make the PETSc shared library?
> If we allow --single-library=0, I do not see how we can avoid this.

Shouldn't MPI static be linked only in libpetscsys? That should work...

Lisandro Dalcin
Research Scientist
Computer, Electrical and Mathematical Sciences & Engineering (CEMSE)
Extreme Computing Research Center (ECRC)
King Abdullah University of Science and Technology (KAUST)

4700 King Abdullah University of Science and Technology
al-Khawarizmi Bldg (Bldg 1), Office # 0109
Thuwal 23955-6900, Kingdom of Saudi Arabia

Office Phone: +966 12 808-0459

More information about the petsc-dev mailing list