Bug 252 - Build breaks when trying to compile fonttosfnt
Summary: Build breaks when trying to compile fonttosfnt
Alias: None
Product: xorg
Classification: Unclassified
Component: * Other (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: highest blocker
Assignee: Kaleb KEITHLEY
QA Contact:
Depends on:
Reported: 2004-03-01 19:19 UTC by Mike A. Harris
Modified: 2011-10-15 15:47 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Description Mike A. Harris 2004-03-01 19:19:01 UTC
CVS checkout from a few hours ago, breaks when compiling fonttosfnt:

gcc -m32 -O2 -march=i386 -mcpu=i686 -fno-strict-aliasing -pipe -ansi -pedantic
-Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes
-Wmissing-declarations -Wredundant-decls -Wnested-externs -Wundef   
-I../../exports/include/X11/fonts -I/usr/include/freetype2 
-I../../exports/include/X11  -I../.. -I../../exports/include   -Dlinux
-DXFREE86_FT2    -c -o read.o read.c
read.c: In function `readFile':
read.c:108: `BDF_PropertyRec' undeclared (first use in this function)
read.c:108: (Each undeclared identifier is reported only once
read.c:108: for each function it appears in.)
read.c:108: parse error before "prop"
read.c:139: warning: implicit declaration of function `FT_Get_BDF_Property'
read.c:139: `prop' undeclared (first use in this function)
read.c:140: `BDF_PROPERTY_TYPE_ATOM' undeclared (first use in this function)
read.c:199: `BDF_PROPERTY_TYPE_INTEGER' undeclared (first use in this function)
make: *** [read.o] Error 1
Comment 1 Mike A. Harris 2004-03-01 19:52:08 UTC
Investigation into problem revealed that the freetype2 on the test
system I was using for the build, had too old of a version of freetype2
installed.  I upgraded it to what is in the tree, and the problem has
gone away.

False alarm, closing as INVALID
Comment 2 Jeremy Huddleston Sequoia 2011-09-27 10:21:56 UTC
Mass update: Close all bugs resolved over one year ago.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.