<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#c10">Comment # 10</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">> ?? so how come this issue is coming? getting
> confused. are you sharing binaries built against
> new SDK with old version of OS X? or who does
> enforce that stupid thing?</span >
Oh! This is actually pretty simple. What I'm actually distributing is a game.
In Mac, like most of the time in windows, you ship the dependencies along with
with an app.
So by my compiling with the latest XCode and SDK, it means nobody running 10.11
or older can run our app. I just submitted the issue (and fix) to macports
after investigating the issue a bit.
<span class="quote">> ?? No, it doesn't break. and? what was added
> without removing?</span >
I think you've got it backwards. Sierra added mkostemp and I don't think it
removed anything. Before that, fontconfig presumably used mkstemp but in
Sierra, since it has mkostemp it will use it and compile/link successfully but
crash when distributed to a system without the latest OS.</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>