The new OS X release 10.11 "El Capitan" has a "security" feature that
prevents passing DYLD_LIBRARY_PATH to child processes. Somehow, that
variable is stripped from the environment.
Consequently, the current in-tree "make check" test setup will no longer
work, because programs such as initdb and psql that are called several
layers down will no longer be pointed to the right libraries. If you
run "make install" before "make check", it will work; otherwise
something will either fail because it can't find the libraries, or it
might pick up libraries found somewhere else, with poor outcomes, in my
experience.
The exact specifications of this new behavior aren't clear to me yet.
For example, this C program works just fine:
```
#include <stdio.h>
#include <stdlib.h>
int
main()
{ printf("DYLD_LIBRARY_PATH = %s\n", getenv("DYLD_LIBRARY_PATH")); return 0;
}
```
but this shell script does not:
```
echo "DYLD_LIBRARY_PATH = $DYLD_LIBRARY_PATH"
```
There is breakage all over the Internet if you search for this, but the
full details don't appear to be very clear.
One workaround is to disable System Integrity Protection, effectively
restoring the behavior of the previous OS release.
Or don't upgrade quite yet if you don't want to deal with this at the
moment.
