[petsc-dev] problems with shared libraries and pragmatic.py

[Satish Balay]

On Thu, 15 Oct 2015, Jed Brown wrote:

> Matthew Knepley <knepley at gmail.com> writes:

> But is this the only way?  Why on earth should the person distributing a
> shared library be the one that needs to make a decision about whether a
> *user* of that library links using RPATH or not?

I believe thats an OSX requirement. I think its more like - the
library should be able to find itself :) [esp when its copied over or
moved arround with 'make install']

We do the same with libpetsc.dylib in config/install.py

Satish