ML symbols in petscksp.so

Jed Brown jed at 59A2.org
Wed Oct 28 16:14:47 CDT 2009


Matthew Knepley wrote:
> You always have to link the ML library if you configure for ML, right?

No, all the third party libs used to be put into the PETSc shared libs
(but not the static libs).  The easiest way to do this is with
-Wl,--whole-archive though I haven't looked at the build system to see
if this is how it is actually being done.  All the others still behave
this way, but ML is no longer included.

So if you are using shared libs, you only need to link libpetsc*.so.
This is recommended practice with shared libs, you only explicitly link
the interface libraries (those that your code actually calls into) and
let the linker handle the dependencies.  Of course when using static
libs, you need to explicitly link all the dependencies.

Jed

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 261 bytes
Desc: OpenPGP digital signature
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20091028/1f60bc07/attachment.sig>


More information about the petsc-dev mailing list