Re: Bug#793137: tulip: FTBFS on armel and armhf - blocks testing migration

[Yann Dirson <ydirson@free.fr>]

On Tue, Jul 21, 2015 at 06:08:45PM +0200, Niels Thykier wrote:
> Source: tulip
> Version: 4.7.0dfsg-1
> Severity: serious
> 
> The tulip package FTBFS on armel and armhf.  Since it has built there
> in the past, this is a regression and by extension prevents migration
> to testing.  Here is a (possibly) relevant part of the build log for
> armhf.

The first error to appear in the log, repeated several times, is:

In file included from /usr/include/arm-linux-gnueabi/qt5/QtGui/qopengl.h:97:0,
                 from /usr/include/arm-linux-gnueabi/qt5/QtOpenGL/qgl.h:39,
                 from /usr/include/arm-linux-gnueabi/qt5/QtOpenGL/qglframebufferobject.h:37,
                 from /usr/include/arm-linux-gnueabi/qt5/QtOpenGL/QGLFramebufferObject:1,
                 from /«PKGBUILDDIR»/library/tulip-gui/src/GlOffscreenRenderer.cpp:26:
/usr/include/GLES3/gl3.h:69:25: error: conflicting declaration 'typedef khronos_ssize_t GLsizeiptr'
 typedef khronos_ssize_t GLsizeiptr;
                         ^
In file included from /«PKGBUILDDIR»/library/tulip-gui/src/GlOffscreenRenderer.cpp:24:0:
/usr/include/GL/glew.h:1663:19: note: previous declaration as 'typedef ptrdiff_t GLsizeiptr'
 typedef ptrdiff_t GLsizeiptr;
                   ^

Those look like conflicting declaration between 2 OpenGL headers,
which on my amd64 box come from libgles2-mesa-dev and libglew-dev.

Isn't there here an arm-specific mismatch between those 2 packages ?