[petsc-users] static libs

[Amil Sharma]

Just wondering if static linking is better for performance?

On Thu, Feb 20, 2020 at 2:58 PM Albert Mollen <amollen at pppl.gov> wrote:

> Hi Mark,
> I'm trying to rebuild Adios2 with dynamic linking on cori. Hopefully we
> can move over to that.
>
> Best regards
> ----------
> Albert Mollén
> Associate Research Physicist
>
> Theory Department
> Princeton Plasma Physics Laboratory
> P.O. Box 451
> Princeton, NJ 08543-0451
> USA
>
> Tel. +1 609-243-3909
> E-mail: amollen at pppl.gov
>
>
> On Thu, Feb 20, 2020 at 2:52 PM Amil Sharma <asharma at pppl.gov> wrote:
>
>> We need static linking in order to link an existing static IO library,
>> but we did not know the PETSc static build configure option.
>>
>> On Thu, Feb 20, 2020 at 2:30 PM Satish Balay <balay at mcs.anl.gov> wrote:
>>
>>> BTW: What do you mean by 'Cray static library environment variable'? Is
>>> it CRAYPE_LINK_TYPE? What is set to? What problems are you having?
>>>
>>> One can get shared library build of PETSc working with:
>>>
>>> export CRAYPE_LINK_TYPE=dynamic
>>>
>>> Satish
>>>
>>> On Thu, 20 Feb 2020, Satish Balay via petsc-users wrote:
>>>
>>> > You can build PETSc statically with configure option:
>>> >
>>> > --with-shared-libraries=0
>>> >
>>> > Satish
>>> >
>>> > On Thu, 20 Feb 2020, Mark Adams wrote:
>>> >
>>> > > We are having problems linking with at Cray static library
>>> environment
>>> > > variable, that is required to link Adios, and IO package. How does
>>> one
>>> > > build with static PETSc libs?
>>> > > Thanks,
>>> > > Mark
>>> > >
>>> >
>>>
>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20200220/531dae1e/attachment.html>