[Fontconfig-bugs] [Bug 102986] mkostemp weak linking on macOS Sierra causes a crash if library is run on 10.11 or older

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=102986

--- Comment #7 from Akira TAGOH <akira at tagoh.org> ---
(In reply to Gregorio Litenstein from comment #6)
> 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

I know.

> 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.

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.

> 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.

That is wrong I'm saying. that works only when everything keeps compatibility.
in this case, that assumption is already broken.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/fontconfig-bugs/attachments/20170926/db16d035/attachment.html>