Description of problem:
freetype returns an "invalid argument" error (6) when rendering character code
32 (if there are no strokes in the glyph) because it leads to allocating a
0-length block of memory and ftutil.c considers that an error.

Version-Release number of selected component (if applicable):
freetype-2.2.1-10

How reproducible:
Always.  An example of a program that is affected by this bug is tuxtype2, which
segfaults immediately on startup (trying to dereference a null pointer).

Steps to Reproduce:
1. Install tuxtype2 from the Fedora 6 Extras collection
2. Run tuxtype2
  
Actual results:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1209043264 (LWP 26955)]
black_outline (t=0x80594c9 "Fish Cascade", font=0xa0b00e0, c=0x805fe28) at
alphabet.c:123
123             out = SDL_CreateRGBSurface(SDL_SWSURFACE, (tmp->w)+5,
(tmp->h)+5, 32, rmask, gmask, bmask, amask);
(gdb) bt
#0  black_outline (t=0x80594c9 "Fish Cascade", font=0xa0b00e0, c=0x805fe28) at
alphabet.c:123
#1  0x0804f51b in TitleScreen_load_menu () at titlescreen.c:75
#2  0x0804fdf4 in TitleScreen () at titlescreen.c:293
#3  0x0804e1b5 in main (argc=2, argv=0xbf888d84) at main.c:151
#4  0x00151f2c in __libc_start_main


Expected results:
Program should display rendered text.


Additional info:
The fix can be found on
http://cvs.savannah.gnu.org/viewcvs/freetype2/src/base/ftutil.c