[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 #12 from Gregorio Litenstein <g.litenstein at gmail.com> ---
> 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.

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

You are always expected to rebuild packages when a new release comes up; 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)

> 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

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.

2 Is not reasonable because it's not like this would break the app on an OS
that is 3 or 4 years old, it was literally second-to-latest major update until
about a week ago.

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

Eventually I have to drop support for older OS, I know that (Until a couple
versions ago we supported 10.6) but it seems a bit... excessive to
all-of-a-sudden drop support for 3 major releases of the OS.

Anyway... Thanks, I guess.

-- 
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/c368de6b/attachment.html>