Help building i810 on Fedora FC3

[Bryan Whitmore]

I'm following the advice at http://dri.freedesktop.org/wiki/Building
using the suggested host.def file.  My build terminates with the
following error:

gcc -m32 -O2 -gstabs+ -pipe -ansi -pedantic -Wall -Wpointer-arith
-Wstrict-prototypes                    -Wmissing-prototypes
-Wmissing-declarations                          -Wredundant-decls
-Wnested-externs -Wundef -fPIC  -I. -I.. -I../../../../include/fonts
-I../../include -I../../../../exports/include/X11
-I../../../../programs/Xserver/include -I/usr/include/freetype2
-I/usr/include/freetype2/config -I../../../../exports/include
-I../../../.. -I../../../../exports/include -I/usr/X11R6/include
-Dlinux -D__i386__ -D_POSIX_C_SOURCE=199309L   -D_POSIX_SOURCE
-D_XOPEN_SOURCE       -D_BSD_SOURCE -D_SVID_SOURCE
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64  -D_GNU_SOURCE             
             -DSHAPE -DXINPUT -DXKB -DLBX -DXAPPGROUP    -DXCSECURITY
-DTOGCUP   -DXF86BIGFONT -DDPMSExtension  -DPANORAMIX     -DRENDER
-DRANDR       -DXFIXES -DDAMAGE -DCOMPOSITE -DXEVIE        
-DGCCUSESGAS -DAVOID_GLYPHBLT -DPIXPRIV -DSINGLEDEPTH              
-DXFreeXDGA -DXvExtension -DXFree86LOADER -DDLOPEN_HACK
-DXFree86Server      -DXF86VIDMODE                          
-DXvMCExtension                   -DSMART_SCHEDULE
 -DBUILDDEBUG -DXResExtension                    
-DX_BYTE_ORDER=X_LITTLE_ENDIAN        -DXORG_VERSION_CURRENT="(((6) *
10000000) + ((8) * 100000) + ((99) * 1000) + 14)" -DNDEBUG  
-DFUNCPROTO=15 -DNARROWPROTO -DIN_MODULE -DXFree86Module 
-DXFREE86_FT2    -c ftfuncs.c
In file included from ftfuncs.c:46:
./ft2build.h:39:38: freetype/config/ftheader.h: No such file or directory
ftfuncs.c:47:10: #include expects "FILENAME" or <FILENAME>
ftfuncs.c:48:10: #include expects "FILENAME" or <FILENAME>
ftfuncs.c:49:10: #include expects "FILENAME" or <FILENAME>
ftfuncs.c:50:10: #include expects "FILENAME" or <FILENAME>
ftfuncs.c:51:10: #include expects "FILENAME" or <FILENAME>
ftfuncs.c:52:10: #include expects "FILENAME" or <FILENAME>
ftfuncs.c:53:10: #include expects "FILENAME" or <FILENAME>
ftfuncs.c:54:10: #include expects "FILENAME" or <FILENAME>
ftfuncs.c:55:10: #include expects "FILENAME" or <FILENAME>
ftfuncs.c:56:10: #include expects "FILENAME" or <FILENAME>
ftfuncs.c:57:10: #include expects "FILENAME" or <FILENAME>
In file included from ftfuncs.c:68:
../ft.h:70: error: syntax error before "FT_CharMap"
../ft.h:70: warning: no semicolon at end of struct or union
../ft.h:73: error: syntax error before '}' token

 . . . (about 225 more syntax errors) . . .

ftfuncs.c:3599: error: syntax error before "pFont"
ftfuncs.c: In function `FreeTypeRasteriseGlyph':
ftfuncs.c:995: warning: statement with no effect
make[6]: *** [ftfuncs.o] Error 1
make[6]: Leaving directory `/usr/src/Xorg/xc/lib/font/FreeType/module'
make[5]: *** [all] Error 2
make[5]: Leaving directory `/usr/src/Xorg/xc/lib/font/FreeType'
make[4]: *** [FreeType] Error 2
make[4]: Leaving directory `/usr/src/Xorg/xc/lib/font'
make[3]: *** [all] Error 2
make[3]: Leaving directory `/usr/src/Xorg/xc/lib'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/usr/src/Xorg/xc'
make[1]: *** [World] Error 2
make[1]: Leaving directory `/usr/src/Xorg/xc'
make: *** [World] Error 2

I'm wondering if my existing Fontconfig contains some badness?  I'm
using the fontconfig-2.2.3-5 RPM and GCC 3.4.  I'm not sure what other
information would be helpful, but I will get a web space set up if
anybody wants to see full files.  Thanks in advance.

Background:
I'm a bit ignorant of X, but I've been plodding along using google and
educated guessing.  So far, I've managed to get my Dell D610 driving
the LCD to 1450x1050x24 or an external monitor to a variety of
resolutions, up to 1600x1200x24, thanks to
i915-20050621-linux.i386.tar.bz2 from
http://dri.freedesktop.org/snapshots/ .  However, xdriinfo tells me:

Xlib:  extension "XFree86-DRI" missing on display ":0.0".
Screen 0: not direct rendering capable.

DVD playback with mplayer only works in various compatability modes
(usually libmpeg2-v0.4.0b), using the CPU as a space-heater and
dropping frames like mad.  This won't do much for battery life on the
road.

So, rather than taking bits and pieces and, I elected to follow CVS.
Ideally, I'd like to eliminate distibution dependencies and see if the
"stock" CVS build has better luck with my hardware.