Thursday, March 10, 2016
DYLD_LIBRARY_PATH and El Capitan
With the release of Firebird 3 RC2 it is time to concentrate properly on the port of Firebird on MacOSX, Firebird 3 was buildable but we don't have a proper installer, ICU is no longer directly included and there
are a number of other bits and pieces that need to be addressed.
The last time I built Firebird 3 was before I upgraded to El Capitan. I did the upgrade to address some issues with the Firebird installer.
Lets just say when I started ny first build I wasn't expecting too many problems....
When we build Firebird on OSX we arbitrarily point to the ICU location (build_environment/firebird/lib), after copying over the files from the initial ICU build, the Firebird build then finds the ICU libraries dynamically (when needed) because DYLD_LIBRARY_PATH is sey to point to the location via prefix.darwin (make.platform).
While the ICU libraries are being built we set the final actual framework install names and locations of the ICU libraries (using -install_name) and they then placed in the appropriate directory of the framework
when the installer is packaged and built.
Every time I tried to build Firebird it would fall over when trying to build msg.fdb with ISQL.
The error was:
"Could not find acceptable ICU library"
which seemed very strange as I know it was placed exactly where it should be and where DYLD_LIBRARY_PATH should be picking it up.
Setting DYLD_LIBRARY_PATH in my default terminal worked successfully, checking DYLD_PRINT_ENV seeemed to show the path being set etc., after much head scratching I eventually put the following line of code into unicode_util.cpp at the function:
When I next ran the build, this is what was returned..
Something very strange was definitely going on. Some further research eventually turned up this thread on the
"Apparently the behaviour is that DYLD_LIBRARY_PATH is prevented from being inherited into any system binaries. E.g. a shell. But specifying it inside a shell script will allow it to be inherited to children of
that shell, unless the child is a protected process in turn."
My reaction was the same as Tom Lane's but expressed in much stronger terms.
The simplest solution to the problem is to turn off System Integrity Protection
via Recovery Mode (Command-R), and then set csrutil disable in a terminal and reboot.
Note that this is a development only issue and will not affect anybody using the built
binaries when the port is complete.