Date: prev next · Thread: first prev next last
2016 Archives by date, by thread · List index


Is it worthwhile asking the RHEL guys to consider creating a Harfbuzz package?

From a comment in that bug I believe the only reason we now statically link Harfbuzz is because 
RHEL doesn't have a package. Previously we also did it was because of ABI stability issues, but 
these are apparently no longer a problem.

Chris

On 19 Feb 2016, at 11:10 PM, Michael Stahl <mstahl@redhat.com> wrote:

On 19.02.2016 10:10, Khaled Hosny wrote:
On Thu, Feb 18, 2016 at 02:36:48PM +0100, Michael Stahl wrote:
On 18.02.2016 14:17, Khaled Hosny wrote:
I don’t think it is just the unit test that is failing, running the
application will most likely crash as well. Building with system
HarfBuzz should fix the issue, until a better fix is found.

commit 549130ab5d9616f7eb5504db31546b386737ccb2 on master should
hopefully fix the problem of VCL exporting conflicting hb_* symbols.

Pranav please tell us if it still crashes.

This fixed the crash for me, it would be nice to backport this to other
active branches since it seems to affect anyone with a recent enough
system HarfBuzz.

okay, great; meanwhile it landed in libreoffice-5-1 as commit
c2f19cda2b0c0ecea69e57bb0ae9a364e939b729, and in libreoffice-5-0 as
commit 395995f03dd640aee28767f6d920901d91dd3bee


_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.