[pkg-wine-party] Bug#768734: wine-gecko-2.21: FTBFS in jessie: mcom_db.h:41:21: fatal error: prtypes.h: No such file or directory

[Lucas Nussbaum]

Source: wine-gecko-2.21
Version: 2.21+dfsg2-1
Severity: serious
Tags: jessie sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20141108 qa-ftbfs
Justification: FTBFS in jessie on amd64

Hi,

During a rebuild of all packages in jessie (in a jessie chroot, not a
sid chroot), your package failed to build on amd64.

Relevant part (hopefully):
> make[8]: Entering directory '/«BUILDDIR»/wine-gecko-2.21-2.21+dfsg2/security/dbm/src'
> i686-w64-mingw32-gcc -mwindows -o /«BUILDDIR»/wine-gecko-2.21-2.21+dfsg2/wine_gecko-2.21-x86/security/dbm/src/db.o -c -O2 -mwindows -mms-bitfields -mnop-fun-dllimport -DXP_PC -UDEBUG -U_DEBUG -DNDEBUG -DWIN32 -D_WINDOWS -DWIN95 -DNSS_ENABLE_ECC -DUSE_UTIL_DIRECTLY -DSTDC_HEADERS -DHAVE_STRERROR -DHAVE_SNPRINTF -DMEMMOVE -D__DBINTERFACE_PRIVATE  -I/build/wine-gecko-2.21QXCLY/wine-gecko-2.21-2.21+dfsg2/wine_gecko-2.21-x86/dist/include/nspr -I/build/wine-gecko-2.21QXCLY/wine-gecko-2.21-2.21+dfsg2/wine_gecko-2.21-x86/dist/include/nspr -I/«BUILDDIR»/wine-gecko-2.21-2.21+dfsg2/wine_gecko-2.21-x86/security/build/../../dist/public/dbm -I/«BUILDDIR»/wine-gecko-2.21-2.21+dfsg2/wine_gecko-2.21-x86/security/build/../../dist/private/dbm -I../../../dbm/include  ../../../dbm/src/db.c
> In file included from ../../../dbm/src/db.c:50:0:
> /«BUILDDIR»/wine-gecko-2.21-2.21+dfsg2/wine_gecko-2.21-x86/security/build/../../dist/public/dbm/mcom_db.h:41:21: fatal error: prtypes.h: No such file or directory
>  #include "prtypes.h"
>                      ^
> compilation terminated.
> make[8]: *** [/«BUILDDIR»/wine-gecko-2.21-2.21+dfsg2/wine_gecko-2.21-x86/security/dbm/src/db.o] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/11/08/wine-gecko-2.21_2.21+dfsg2-1_jessie.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.