On 13 June 2017 at 04:25, Robert Haas wrote:
> I have a new MacBook Pro running Sierra.
Congratulations.
> 'make check' was failing: 'psql' repeatedly died with an abort
> trap. Binaries worked fine when I ran them from the command line
> (sometimes with DYLD_LIBRARY_PATH, if needed) but when
Simon Riggs writes:
> On 13 June 2017 at 04:25, Robert Haas wrote:
>> 'make check' was failing: 'psql' repeatedly died with an abort
>> trap. Binaries worked fine when I ran them from the command line
>> (sometimes with DYLD_LIBRARY_PATH, if needed) but when run via
>> pg_regress, nothing worked
On 6/12/17 23:38, Tom Lane wrote:
> https://www.postgresql.org/message-id/26098.1446697...@sss.pgh.pa.us
>
>> My main purpose in writing this email is to pass along what I learned
>> in the hopes of sparing somebody else some trouble, but perhaps there
>> is a way to modify our regression test set
Robert Haas writes:
> ... it turns out that System Integrity Protection
> feature *also* prevents DYLD_LIBRARY_PATH from being inherited by
> child processes in some manner.
Yeah, this was already known and documented on the lists a year or two
back. I suggest filing a bug report with Apple; if
I have a new MacBook Pro running Sierra. I managed to get PostgreSQL
to build after install Xcode, installing MacPorts, installing the
documentation toolchain via some incantation that was apparently
wrong, and then uninstalling and reinstalling the documentation
toolchain per https://trac.macport
