GNOME Bugzilla – Bug 752646
Fails to link with Pango when x11 backend disabled
Last modified: 2015-07-20 23:00:06 UTC
If the GTK+ stack is compiled without X11 (i.e. no libx11 present, X backend disabled in gtk+), GTK+ 3.16.4 fails to link: | ./.libs/libgtk-3.so: undefined reference to `PANGO_FC_FONT_MAP' | ./.libs/libgtk-3.so: undefined reference to `PANGO_IS_FC_FONT_MAP' (longer log at https://autobuilder.yoctoproject.org/main/builders/nightly-no-x11/builds/4/steps/BuildImages/logs/stdio) As those are macros, I'm guessing pango-fcfontmap.h gets indirectly included somewhere and not explicitly.
Aha | /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-no-x11/build/build/tmp/work/core2-64-poky-linux/gtk+3/3.16.4-r0/gtk+-3.16.4/gtk/gtksettings.c:3053:7: warning: implicit declaration of function 'PANGO_IS_FC_FONT_MAP' [-Wimplicit-function-declaration] | if (PANGO_IS_FC_FONT_MAP (fontmap) && !FcConfigUptoDate (NULL)) | ^ | /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-no-x11/build/build/tmp/work/core2-64-poky-linux/gtk+3/3.16.4-r0/gtk+-3.16.4/gtk/gtksettings.c:3053:7: warning: implicit declaration of function 'FcConfigUptoDate' [-Wimplicit-function-declaration] | /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-no-x11/build/build/tmp/work/core2-64-poky-linux/gtk+3/3.16.4-r0/gtk+-3.16.4/gtk/gtksettings.c:3055:11: warning: implicit declaration of function 'pango_fc_font_map_cache_clear' [-Wimplicit-function-declaration] | pango_fc_font_map_cache_clear (PANGO_FC_FONT_MAP (fontmap)); | ^ | /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-no-x11/build/build/tmp/work/core2-64-poky-linux/gtk+3/3.16.4-r0/gtk+-3.16.4/gtk/gtksettings.c:3055:11: warning: implicit declaration of function 'PANGO_FC_FONT_MAP' [-Wimplicit-function-declaration] | /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-no-x11/build/build/tmp/work/core2-64-poky-linux/gtk+3/3.16.4-r0/gtk+-3.16.4/gtk/gtksettings.c:3056:11: warning: implicit declaration of function 'FcInitReinitialize' [-Wimplicit-function-declaration] | if (FcInitReinitialize ()) | ^
*** This bug has been marked as a duplicate of bug 751625 ***