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

[Munson, Todd S.]

Satish can you try it from an account that does not have admin privileges?

Todd.

> On Oct 7, 2015, at 4:08 PM, Jed Brown <jed at jedbrown.org> wrote:
> 
> 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.