Bug#733356: swfmill: FTBFS: swft/swft_import_ttf.cpp:17:31: fatal error: freetype/tttables.h: No such file or directory

[David Suárez]

Source: swfmill
Version: 0.3.2-1
Severity: serious
Tags: jessie sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20131226 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

On the new 2.5 version the headers are located at
'/usr/include/freetype2/ftglyph.h' instead of
'/usr/include/freetype2/freetype/ftglyph.h' like in previous versions.

Relevant part (hopefully):
> x86_64-linux-gnu-g++ -DPACKAGE_NAME=\"swfmill\" -DPACKAGE_TARNAME=\"swfmill\" -DPACKAGE_VERSION=\"0.3.2\" -DPACKAGE_STRING=\"swfmill\ 0.3.2\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"swfmill\" -DVERSION=\"0.3.2\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_ICONV=1 -DICONV_CONST= -I.    -I/usr/include/libxml2   -I/usr/include/libxml2   -I/usr/include/libxml2   -I/usr/include/freetype2   -I/usr/include/libpng12    -I./swft/ -I./xslt/ -g -O2 -MT swft/swfmill-swft_import_ttf.o -MD -MP -MF swft/.deps/swfmill-swft_import_ttf.Tpo -c -o swft/swfmill-swft_import_ttf.o `test -f 'swft/swft_import_ttf.cpp' || echo './'`swft/swft_import_ttf.cpp
> swft/swft_import_ttf.cpp:17:31: fatal error: freetype/tttables.h: No such file or directory
>  #include <freetype/tttables.h>
>                                ^
> compilation terminated.
> make[3]: *** [swft/swfmill-swft_import_ttf.o] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/12/26/swfmill_0.3.2-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.