On Mon, Jun 05, 2006 at 06:58:11PM +0200, Josselin Mouette wrote: > Le lundi 05 juin 2006 à 13:38 +0200, Julien Danjou a écrit : > > > fcfreetype.c:53:10: error: #include expects "FILENAME" or <FILENAME> > > > fcfreetype.c:58:10: error: #include expects "FILENAME" or <FILENAME> > > > fcfreetype.c:59:10: error: #include expects "FILENAME" or <FILENAME> > > > fcfreetype.c:60:10: error: #include expects "FILENAME" or <FILENAME>
> Hurray hurray! > OK, I think fontconfig is at fault here, as it is using internal symbols > from freetype, however freetype developers could have tested it against > the most widespread library using it... They did, and the current upstream version of fontconfig is fixed now to not abuse freetype internals in this manner. For fontconfig 2.3.2, a patch is available at <http://www.freetype.org/freetype2/patches/fontconfig-2.3.2-noftinternals.patch>. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/
