[Pkg-javascript-devel] Bug#759843: node-mapnik: FTBFS: vector_tile_processor.hpp:48:38: fatal error: mapnik3x_compatibility.hpp: No such file or directory

[Lucas Nussbaum]

Source: node-mapnik
Version: 1.2.3-1
Severity: serious
Tags: jessie sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20140830 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/«PKGBUILDDIR»/build'
> gyp info spawn make
> gyp  CXX(target) Release/obj.target/_mapnik/src/node_mapnik.o
>  info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
>   CXX(target) Release/obj.target/_mapnik/src/mapnik_map.o
> In file included from ../src/mapnik_map.cpp:10:0:
> /usr/include/vector_tile_processor.hpp:48:38: fatal error: mapnik3x_compatibility.hpp: No such file or directory
>  #include "mapnik3x_compatibility.hpp"
>                                       ^
> compilation terminated.
> make[2]: *** [Release/obj.target/_mapnik/src/mapnik_map.o] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2014/08/30/node-mapnik_1.2.3-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. The build
was done with DEB_BUILD_OPTIONS="parallel=4", so if your packaging tries
to support this, it might be a good idea to explore whether this might
be the cause of the failure.