Re: libXft won't compile: FC_HINT_STYLE undeclared
Peter Winton <[email protected]> Wed, 25 Feb 2004 14:17:04 -0500
| Newsgroups | gmane.comp.freedesktop.xlibs.general |
|---|---|
| Organization | Rose-Hulman Institute of Technology |
| Message-ID | <[email protected]> |
On Tuesday 24 February 2004 08:37 am, Jan van Dijk wrote: > On Monday 23 February 2004 20:54, Peter Winton wrote: > > I'm trying to build libXft-2.1.3 but get the error > > > > gcc -DHAVE_CONFIG_H -I. -I. -I. -I/usr/local/include > > -I/usr/local/include/freetype2 -I/usr/local/include -I/usr/local/include > > -I/usr/X11R6/include -g -O2 -MT xftdpy.lo -MD -MP -MF .deps/xftdpy.Tpo -c > > xftdpy.c -fPIC -DPIC -o .libs/xftdpy.o > > xftdpy.c: In function `_XftDefaultInit': > > xftdpy.c:380: `FC_HINT_STYLE' undeclared (first use in this function) > > xftdpy.c:380: (Each undeclared identifier is reported only once > > xftdpy.c:380: for each function it appears in.) > > xftdpy.c: In function `XftDefaultSubstitute': > > xftdpy.c:478: `FC_HINT_STYLE' undeclared (first use in this function) > > xftdpy.c:482: `FC_HINT_FULL' undeclared (first use in this function) > > make[1]: *** [xftdpy.lo] Error 1 > > make[1]: Leaving directory `/root/src/gtk/libXft-2.1.3' > > make: *** [all] Error 2 > > The fontconfig repository at freedesktop tells me these defines were > introduced in fontconfig version 2.2.91. The obvious patch to Xft's > configure.ac follows. > > Bye, Jan. > > jan-neN/[email protected]:~/src/xlibs $ cvs diff Xft > Index: Xft/configure.ac > =================================================================== > RCS file: /cvs/xlibs/Xft/configure.ac,v > retrieving revision 1.16 > diff -r1.16 configure.ac > 89c89 > < PKG_CHECK_MODULES(FONTCONFIG, fontconfig >= 1.0.1) > --- > > > PKG_CHECK_MODULES(FONTCONFIG, fontconfig >= 2.2.91) This patch doesn't work for me; I get the same error. pkg-config reports that I have fontconfig 2.2.92 since I got it from CVS, so a "good version" result is obtained with or without the patch. It seems that I have the right version of fontconfig. Any ideas what might still be causing this problem? Peter