Re: fontconfig error

[Michael Ekstrand <michael elehack net>]

On Sun, 2006-08-27 at 12:44 -0700, Sergei Steshenko wrote:
> 
> --- Michael Ekstrand <michael elehack net> wrote:
> 
> > On Sat, 2006-08-26 at 20:40 -0400, Bill Cunningham wrote:
> > > > This is your first error message:
> > > >
> > > > "
> > > >      84
> > > 
> > > gcc -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/local/include/freetype2 -I/usr/local
> > > /include
> > > > -I/usr/local/include -DFONTCONFIG_PATH=\"/usr/local/etc/fonts\" -I.. -I../
> > > src -g -O2 -MT
> > > > fcfreetype.l
> > > >      84 o -MD -MP -MF .deps/fcfreetype.Tpo -c fcfreetype.c  -fPIC -DPIC -o
> > > .libs/fcfreetype.o
> > > >      85 fcfreetype.c:53:10: #include expects "FILENAME" or <FILENAME>
> > > >
> > > > ".
> > > >
> > > > And it is exactly the same error message which caused me to file
> > > > already mentioned bug report:
> > > >
> > > > https://bugs.freedesktop.org/show_bug.cgi?id=7862
> > > > .
> > > >
> > > > Did you read the bug report and did you compare my report with
> > > > your error message ?
> > > >
> > > > I have no idea how to fix this.
> > 
> > It looks like a result of FreeType's housecleaning..  The latest
> > versions of freetype removed the public install of old internal headers,
> > which half the projects on the Internet (it seems) used.  They were
> > never supposed to, but they did.  Result: many packages are broken.
> 
> Do your words in simple English mean that fontconfig folks release
> packages which can't compile ?
> 
> That is, they release packages not even trying to compile them ?

No.  They release packages which use internal/experimental FreeType
headers, which up through 2.1, FreeType had installed.  The FreeType
folks released these so developers could experiment with new features
and concepts, but never intended for the features to be used in released
code.  With 2.2, they removed these headers, so that only the
documented, public API's are exposed.  fontconfig used the old headers.
It will build fine with freetype 2.1.x, but not 2.2.  fontconfig is
"broken" in that it uses internal/undocumented API's, but not "broken"
in the sense of them failing to test.  The problem is fixed in
FontConfig 2.3.93 and later.

The following page has all the details:

http://freetype.sourceforge.net/freetype2/freetype-2.2.0.html

> > Installing an older freetype (2.1.x I believe) is an intermediate fix;
> > otherwise, there are patches from freetype's website for some packages,
> > and many packages have appropriate fixes already.
> 
> Could you please be more specific about the patches ? I.e., could you please
> provide URLs to the patches ?

URL above has a link to freetype's info and patch page.

- Michael

-- 
mouse, n.: a device for pointing at the xterm in which you wish to type
        -- Fortune file
Visit me on the Web: http://www.elehack.net/michael