webkit-gtk @1.6.3 - Configure error - build failure

[macports1@…]

I'm building webkit wih +quartz and it is complaining about the missing package xrender.

[jeremyhu (Jeremy Huddleston Sequoia)]

Looks like a bug in configure.ac ... they add a check for xrender even if quartz is chosen:

# check for XRender under Linux/Unix. Some linkers require explicit
# linkage (like GNU Gold), so we cannot rely on GTK+ pulling XRender
if test "$os_win32" = "no"; then
   PKG_CHECK_MODULES([XRENDER], [xrender])
   AC_SUBST([XRENDER_CFLAGS])
   AC_SUBST([XRENDER_LIBS])
fi

[jeremyhu (Jeremy Huddleston Sequoia)]

​https://bugs.webkit.org/show_bug.cgi?id=84095

[chief1983@…]

XRender check fix in the Configure in the MacPorts tar of the source

[chief1983@…]

Patch to portfile to use xrender check patch

[chief1983@…]

I made a patch to the port to work around this for the time being, but it gets stopped on a build error now. Attaching the log too.

[chief1983@…]

Log of build after applying my patch

[jeremyhu (Jeremy Huddleston Sequoia)]

Thanks for the patch. I got sidetracked with other stuff.

The error you're getting is:

error: pango/pangocairo.h: No such file or directory

That makes me think it's missing a dependency on the pango port. Do you have pango installed? gtk2 depends on pango, so that's a bid odd. FWIW:

$ port contents pango | grep cairo
  /opt/local/include/pango-1.0/pango/pangocairo.h
  /opt/local/lib/libpangocairo-1.0.0.dylib
  /opt/local/lib/libpangocairo-1.0.a
  /opt/local/lib/libpangocairo-1.0.dylib
  /opt/local/lib/libpangocairo-1.0.la
  /opt/local/lib/pkgconfig/pangocairo.pc

But that is of course with the +x11 pango variant.

Ryan knows more about pango than I do, so looping him in.

[jeremyhu (Jeremy Huddleston Sequoia)]

r92131 has the xrender-check patch.

Regarding the pango bits, I see "-I./Source/WebCore/platform/graphics/pango" in your CFLAGS, but I don't see -I${prefix}/include/pango-1.0 like I would expect.

[jeremyhu (Jeremy Huddleston Sequoia)]

In #24622 (which added the variant), they set the font backend to be pango instead of freetype for the +quartz variant. I don't see why.

What happens if you delete the "--with-font-backend=pango" from your configure.args (make sure you have freetype installed)

[jeremyhu (Jeremy Huddleston Sequoia)]

Also, I see the same failure with +x11 if I change the font backend to pango.

​https://bugs.webkit.org/show_bug.cgi?id=77832

[jeremyhu (Jeremy Huddleston Sequoia)]

I think r92135 should fix this now. Please reopen or file a new bug if there are additional issues.

[ryandesign (Ryan Carsten Schmidt)]

Apparently still a problem; see #34134.