Hi,
on the archive I found this posting.
Robert Newell Jr submariner47@hotmail.com
Wed, 10 Dec 2003 21:43:53 -0500> hello, i tried to compile fontconfig and received the following
> output:[root@Jubei fontconfig-2.2.0]# make
> make all-recursive
> make[1]: Entering directory `/usr/src/fontconfig-2.2.0''
> Making all in fontconfig
> make[2]: Entering directory `/usr/src/fontconfig-2.2.0/fontconfig''
> make[2]: Nothing to be done for `all''.
> make[2]: Leaving directory `/usr/src/fontconfig-2.2.0/fontconfig''
> Making all in fc-lang
> make[2]: Entering directory `/usr/src/fontconfig-2.2.0/fc-lang''
> gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../src -I/usr/local/include
> -I/usr/local/incl
> ude/freetype2 -g -O2 -c fc-lang.c
> In file included from ../src/fcint.h:39,
> from fc-lang.c:25:
> ../fontconfig/fcfreetype.h:30: parse error before
> `FcFreeTypeCharIndex''../fontconfig/fcfreetype.h:30: parse error
before
> `face''../fontconfig/fcfreetype.h:30: warning: data definition has
no
> type or storage c
> lass
> ../fontconfig/fcfreetype.h:33: parse error before `face''
> ../fontconfig/fcfreetype.h:36: parse error before `face''
> ../fontconfig/fcfreetype.h:39: parse error before `FT_Face''
> ../fontconfig/fcfreetype.h:42: parse error before `f''
> In file included from fc-lang.c:25:
> ../src/fcint.h:497: parse error before `encoding''
> make[2]: *** [fc-lang.o] Error 1
> make[2]: Leaving directory `/usr/src/fontconfig-2.2.0/fc-lang''
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/usr/src/fontconfig-2.2.0''
> make: *** [all-recursive-am] Error 2
> [root@Jubei fontconfig-2.2.0]#
> does anyone know what is wrong?
> your help appreciated in advance,
I had the same problem and found
the reason: You''ve to install freetype2, e.g.
freetype-2.1.5.tar.bz2 is working here. That will put the necessary
headerfiles in place and the errors go away.
I still have a problem so:
I am running the make install and it will break on running ft-cache for
the URW font folder (segfaults). It contains 43 fonts (If you want to
know which please ask by direct mail as I''m not subscribed). Is anybody
interested in debugging this? I can go through the font list and try to
find out which font exactly is the culprit.
K.-H.