On Wed, Oct 27, 2004 at 03:02:52PM +0400, Dmitry V. Levin wrote:
> Похоже, что новый freetype2-devel сломал сборку реально использующих его
> пакетов; перестали собираться нижеперечисленные пакеты:
> avifile-0.738-alt0.6
> bootsplash-3.0.7-alt1
> camlimages-2.11-alt9.1
> clanlib-0.6.5-alt1.3
> gd1-1.8.4-alt7
> gnome-print-0.36-alt6
> python-module-imaging-1.1.4-alt8
> SDL_ttf-2.0.6-alt2.1
> xpdf-3.00-alt2
> 
> Вот, например, лог сборки пакета bootsplash:
[...]
> gcc -Os -Wall -I/usr/include/freetype2   -c -o ttf.o ttf.c
> In file included from ttf.c:13:
> /usr/include/freetype2/freetype/freetype.h:20:2: #error "`ft2build.h' hasn't been included yet!"
> /usr/include/freetype2/freetype/freetype.h:21:2: #error "Please always use macros to include FreeType header files."
> /usr/include/freetype2/freetype/freetype.h:22:2: #error "Example:"
> /usr/include/freetype2/freetype/freetype.h:23:2: #error "  #include <ft2build.h>"
> /usr/include/freetype2/freetype/freetype.h:24:2: #error "  #include FT_FREETYPE_H"
> make: *** [ttf.o] Error 1

RTFM (/usr/share/doc/freetype2-2.1.9/docs/CHANGES):
[...]
LATEST CHANGES BETWEEN 2.1.6 and 2.1.5
[...]
  III. MISCELLANEOUS

    - There  is now  a guard  in the  public header  files  to protect
      against inclusion of freetype.h from FreeType 1.

    - Direct inclusion of freetype.h  and other public header files no
      longer works.  You have to use the documented scheme

        #include <ft2build.h>
        #include FT_FREETYPE_H

      to load freetype.h with  a symbolic name.  This protects against
      renaming  of public  header  files (which  shouldn't happen  but
      actually  has, avoiding two  public header  files with  the same
      name).


P.S. Кто так сильно хотел новый freetype2?


-- 
ldv