[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 #13 from Akira TAGOH <akira at tagoh.org> ---
(In reply to Gregorio Litenstein from comment #12)
> No... I understand this, but don't agree with you. I think libraries should
> be able to adapt their build/configuration settings for different systems
> when they're things as small as this.

I do. it is obvious thing as it always works when you build it on the proper
env with the proper deps of libraries.

> You are always expected to rebuild packages when a new release comes up;

Yes, because it is safest way to keep compatibility and check it at the build
time. this would helps to avoid a trouble at the runtime like what you are
facing at this moment.

> most of the time they will still be compatible, but not always. Nonetheless,
> macports has an option (not by default) to target a specific version of OSX.
> Generally I target my releases for 10.9 (i.e. try to provide compatibility
> for as-far-back as possible)

Sure. so the problem should be that your target release is different with the
target release on macports then. if you build fontconfig against 10.9 which
shouldn't have mkostemp in the system library, it should works fine. so another
option would be to build fontconfig yourself and statically link it to avoid
using one installed on the users' system and/or statically link everything to
avoid such situation.

> 1 Makes no sense considering the actual requirement for compatibility is
> something so small. TBH I already submitted the fix to macports but was
> more-or-less playing devil's advocate in case you could be persuaded to
> implement it in your build system.

unlikely. otherwise I can't use any symbols from libraries to settle deps on
various releases of OSes and have to implement everything. our target OS isn't
only OS X.
so I do support the compatibility and the portability in the source code level
as much as possible.

> 3 It's certainly easier to configure fontconfig to ignore mkostemp as it was
> doing before.

Apparently you don't get what I meant. you better learn how the shared library
works.

-- 
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/20170928/8243db05/attachment-0001.html>