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

[Jed Brown]

Satish Balay <balay at mcs.anl.gov> writes:

> And it works fine from C code.

Yes, but /usr/bin/python is also C code, so how does the OS recognize
it?  Is it by name, or some token, or some heuristic?  Does linking my
program to libpython.so cause the OS to futz with my environment?  Does
naming my C program "python" change its environment?  This "feature"
seems horribly inconsistent and ineffective.  I'd like to hear the
rationale for it.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20151007/de169e7c/attachment.sig>