<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#c11">Comment # 11</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:akira@tagoh.org" title="Akira TAGOH <akira@tagoh.org>"> Akira TAGOH</a> <pre>let me try to say again, your understanding of the binary compatibility is quite poor. I don't see why you think you could re-use the binary which depends on the incompatible system library. you can do that *only* when the required symbols from libraries isn't missing. in this case, fontconfig binary built against new system library doesn't work with old one *because* mkostemp wasn't available there. I didn't see how macports was working though, after some conversation with you, they seem expecting to rebuild from the source to use. i.e. they didn't guarantee the binary compatibility between releases. that's true. An action you can take would be: 1) to provide your app built against the proper deps on both OSes. 2) to stop supporting older OS for your app. 3) to make an wrapper library for mkostemp for old OS Anyway, this isn't our bug.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>