[Webkit-unassigned] [Bug 108174] New: [GTK] Missing build flags when building with Harfbuzz
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Tue Jan 29 02:39:36 PST 2013
https://bugs.webkit.org/show_bug.cgi?id=108174
Summary: [GTK] Missing build flags when building with Harfbuzz
Product: WebKit
Version: 528+ (Nightly build)
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Keywords: Gtk
Severity: Normal
Priority: P2
Component: WebKit Gtk
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: mario at webkit.org
CC: mrobinson at webkit.org, cgarcia at igalia.com,
pnormand at igalia.com
I've been experiencing for some time the following kind of linking errors when building WebKitGTK+ in certain scenarios (e.g. trying to build it with build-webkit inside a jhbuild shell environment for GNOME development over a Ubuntu 12.04 64bit machine):
./.libs/libwebkit2gtk-3.0.so: undefined reference to `hb_icu_script_to_script'
Investigating a bit the issue I realized the problem was that the -lharfbuzz parameter was not present in the linking lines, which was the cause of the error. Investigating a bit further I found out that the $(FREETYPE_CFLAGS) and $(FREETYPE_LIBS) variables were not being added in most of the places in GNUMakefile.am files where binaries were built, so that's why the -lharfbuzz parameter was not added.
I'm still not sure why this issue is not spotted in some other environments (doing a clean build with build-webkit script *outside* my jhbuild for GNOME does not hit the issue) but it seems interesting to me in any case to add these flags to GNUMakefile.am files where needed, since that fixes the issue in these other specific cases, while it leaves the other scenarios working properly as well.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list