* Phil Race:
> Upgrade to harfbuzz 2.8
I believe this causes a build failure with GCC 8.3 (from Debian
buster):
* For target
support_native_java.desktop_libfontmanager_hb-ot-shape-complex-use.o:
In file included from
…/jdk/src/java.desktop/share/native/libharfbuzz/hb-ot-shape-complex-use.cc:33
On Fri, 12 Feb 2021 12:22:44 GMT, Vladimir Kempik wrote:
>> src/hotspot/os_cpu/bsd_aarch64/os_bsd_aarch64.cpp line 435:
>>
>>> 433: //||\ Java thread created by VM does not
>>> have glibc
>>> 434: //|glibc guard page| - guard, attached Java thread usuall
* Philip Race:
> There is more code in the newer version but not 4 times as much !
> Harfbuzz now requires c++11 features (-std=c++11)
> Possibly the C++ compiler you are using (you don't mention platform) is
> slower in this mode.
It's GCC 8 on Debian buster, which defaults to C++14. And it's
* Phil Race:
> This upgrades JDK to import the current 2.7.2 version of harfbuzz -
> an OpenType text shaping library
>
> https://bugs.openjdk.java.net/browse/JDK-8247872
>
> This has passed building and headless and headful automated tests on
> all platforms.
Is it just me, or does the new Harfb
* Omair Majid:
> Basically, there is one file there (LCMS.c) that I want to make sure
> that does not get compiled against the headers located in the same
> directory. One way to be absolutely certain is to move the files out of
> that directory into another. `#include <..>` rather than `#include
