<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTOURBUG - mkostemp weak linking on macOS Sierra causes a crash if library is run on 10.11 or older" href="https://bugs.freedesktop.org/show_bug.cgi?id=102986#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTOURBUG - mkostemp weak linking on macOS Sierra causes a crash if library is run on 10.11 or older" href="https://bugs.freedesktop.org/show_bug.cgi?id=102986">bug 102986</a> from <a class="email" href="mailto:g.litenstein@gmail.com" title="Gregorio Litenstein <g.litenstein@gmail.com>"> Gregorio Litenstein</a> <pre>It actually makes perfect sense but I thnk you don't actually understand what I'm trying to say. mkostemp is provided not by macports but by a core/standard macOS library present in the SDK, which resides in /usr/lib/libSystem.B.dylib During building, fontconfig checks where the function exists, if one is using the 10.12 SDK (or newer), it does and it builds under that assumption. Since this function lives in a core library, it is weakly linked, and it definitely makes no sense to want to ship core system libraries (not to mention it would probably be against EULA and/or copyright) with a project. So, if this version of fontconfig is run on any older version of macOS (like 10.11.6), it will look for mkostemp in libSystem.B.dylib, and since it isn't there, the library crashes.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>