Bug 54636 – emerge directfb fails; freetype 2.1.5-r1 suspected culprit

• Product: Gentoo Linux
• Status: RESOLVED INVALID

[Description Benjamin Paul Kay 2004-06-21 07:15:44 UTC]

When emerging diretfb 0.9.20, build fails when trying to compile a file called "idirectfbfont_ft2". There are several hundred lines of error messages that look like this:
/usr/include/freetype2/freetype/ftglyph.h:3034: error stray '\24' in program
Of course, "3034" varies depending on the line number. There are also warnings mixed in with said error messages that look something like this:
/usr/include/freetype2/freetype/ftglyph.h:3034:134: warning: null character(s) ignored
So I'm not actually sure whether this is a but in freetype of directfb.


Reproducible: Always
Steps to Reproduce:
1. emerge sync
2. emerge directfb
3. ...





My USE flags:
acl acpi adns apache2 apm bidi crypt curl directfb fastcgi fbcon ggi gpm
hardened ipv6 java jpeg ldap libwww memlimit mmx mpi ncurses nocardbus odbc
offensive pam pcre perl pic pie png pnp python readline ruby slang sse ssl svga
tcpd unicode usb vhosts xml xml2 zlib -apm -arts -bonobo -cdr -X -gnome -kde -qt

My chost: i686-pc-linux-gnu

My CFLAGS/CXXFLAGS: -march=pentium3 -03 -pipe -fomit-frame-pointer
-funroll-loops -fstack-protector

My /etc/make.conf also contains the line:
VIDEO_CARDS="nvidia"
(I have a Riva TNT card). emerge directfb fails with or without this line in
/etc/make.conf

Other relavent stuff from emerge info:
Portage 2.0.50-r8 (default-x86-2004.0, gcc-3.3.3, glibc-2.3.3-20040420-r0,
2.4.24-hardened-r3
Gentoo base system version 1.4.16
autoconf-2.59-r3
automake-1.8.3
accept_keywords="x86"
autoclean="yes"
compiler="gcc3"
features="autoaddcvs ccache sandbox"
makeopts-"-j2"

Sorry about the shorthand, but I had to copy all of this stuff by hand.

[Comment 1 Benjamin Paul Kay 2004-06-21 11:11:44 UTC]

I examined the offending freetype file and discovered it was complete gibberish. I then unmerged freetype, deleted all the freetype distfiles, and emerged freetype. This resolved the problem. Simply remerging freetype did NOT solve the problem. Ah, life's little mysteries... anyways, chances are nobody else is having this bug.