<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><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#c8">Comment # 8</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 <span class="vcard"><a class="email" href="mailto:g.litenstein@gmail.com" title="Gregorio Litenstein <g.litenstein@gmail.com>"> <span class="fn">Gregorio Litenstein</span></a>
</span></b>
<pre><span class="quote">> I know that too. thus, I'm suggesting you or probably macports should provides binanries per releases which is built against the proper deps of libraries. I didn't hear the reason yet why they don't do that.</span >
Macports for the most part builds from source and requires a reinstall and
rebuild of all packages on every major OS upgrade.
<span class="quote">> That is wrong I'm saying. that works only when everything keeps compatibility. in this case, that assumption is already broken.</span >
Adding a function (without removing anything) shouldn't break compatibility,
should it?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>