[petsc-dev] Mac OS X El Capitan does not propagate DYLD_LIBRARY_PATH from parent process

Andrs, David david.andrs at inl.gov
Wed Oct 7 17:31:44 CDT 2015

On Wed, Oct 7, 2015 at 4:09 PM, Satish Balay <balay at mcs.anl.gov> wrote:

> On Wed, 7 Oct 2015, Andrs, David wrote:
> > As I said before the fix here is to link libomp.dylib using the absolute
> > path, i.e. we need to do something on our end. It is not a bug in PETSc's
> > build system. I just wanted to give you guys a heads up, because some
> users
> > might run into a similar issue...
> BTW: what do you have for 'mpicc -show'
> [configure.log you sent earlier didn't get far enough to caputure that]
> also good to know:
> mpicc -v foo.c [on any test code]

Sorry, I can't provide that. ​We do not have the broken compiler​ around

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20151007/9f0dd451/attachment.html>

More information about the petsc-dev mailing list