Date: Wed, 23 Apr 2025 12:07:46 +0000 From: bugzilla-noreply@freebsd.org To: java@FreeBSD.org Subject: [Bug 286288] java/openjdk11: use system harfbuzz, ccache, etc. Message-ID: <bug-286288-8522-TWHzIV3eRp@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-286288-8522@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286288 Mikhail T. <freebsd-2024@virtual-estates.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |freebsd-2024@virtual-estate | |s.net --- Comment #2 from Mikhail T. <freebsd-2024@virtual-estates.net> --- (In reply to Harald Eilertsen from comment #1) > The ports for OpenJDK 17 and upwards already use the system harfbuzz I just tested java/openjdk17 and found the same problem I alluded to earlier. In the absence of the bundled libharfbuzz -- which absence can (and should!) be achieved by adding the --exclude libharfbuzz to the EXTRACT_AFTER_ARGS -- the build fails due to absence of the library's main header: /usr/ports/java/openjdk17/work/jdk17u-jdk-17.0.15-6-1/src/java.desktop/share/native/libfontmanager/HBShaper.c:28:10: fatal error: 'hb.h' file not found 28 | #include "hb.h" | ^~~~~~ 1 error generated. Clearly, this error does not occur, when the bundled library is not excluded, which means, the bundled header is always used, even when --with-harfbuzz=system is used. The patch I submitted yesterday modifies the make/lib/Awt2dLibraries.gmk to avoid the build-failure, when libharfbuzz is omitted, which should be good enough for our port. However, it may not be enough for when the bundled code is extracted as usual -- and the bundled header may be used with the system-provided library. The problem should be communicated upstream -- but their ticketing system is not open... -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-286288-8522-TWHzIV3eRp>