Source: glew
Version: 2.1.0-2
Severity: serious
Control: affects -1 + src:pymol

Hi,

I just noticed that pymol stated to FTBFS, this seems to be caused by
glew (which was updated recently, while libglvnd hasn't seen changes
for some time):

In file included from layer0/os_gl.h:60,
                 from layer1/Ortho.h:28,
                 from layer0/Err.cpp:22:
/usr/include/GL/glext.h:12066:105: error: conflicting declaration 'typedef void 
(* PFNGLFRAGMENTLIGHTFVSGIXPROC)(GLenum, GLenum, const GLfloat*)'
 typedef void (APIENTRYP PFNGLFRAGMENTLIGHTFVSGIXPROC) (GLenum light, GLenum 
pname, const GLfloat *params);
                                                                                
                         ^
In file included from layer0/os_gl.h:58,
                 from layer1/Ortho.h:28,
                 from layer0/Err.cpp:22:
/usr/include/GL/glew.h:18734:28: note: previous declaration as 'typedef void (* 
PFNGLFRAGMENTLIGHTFVSGIXPROC)(GLenum, GLenum, GLfloat*)'
 typedef void (GLAPIENTRY * PFNGLFRAGMENTLIGHTFVSGIXPROC) (GLenum light, GLenum 
pname, GLfloat* params);
                            ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from layer0/os_gl.h:60,
                 from layer1/Ortho.h:28,
                 from layer0/Err.cpp:22:
/usr/include/GL/glext.h:12068:103: error: conflicting declaration 'typedef void 
(* PFNGLFRAGMENTLIGHTIVSGIXPROC)(GLenum, GLenum, const GLint*)'
 typedef void (APIENTRYP PFNGLFRAGMENTLIGHTIVSGIXPROC) (GLenum light, GLenum 
pname, const GLint *params);
                                                                                
                       ^
In file included from layer0/os_gl.h:58,
                 from layer1/Ortho.h:28,
                 from layer0/Err.cpp:22:
/usr/include/GL/glew.h:18736:28: note: previous declaration as 'typedef void (* 
PFNGLFRAGMENTLIGHTIVSGIXPROC)(GLenum, GLenum, GLint*)'
 typedef void (GLAPIENTRY * PFNGLFRAGMENTLIGHTIVSGIXPROC) (GLenum light, GLenum 
pname, GLint* params);
                            ^~~~~~~~~~~~~~~~~~~~~~~~~~~~

and so on...

Full log attached. This happens with both pymol in sid and experimental.


Andreas

Attachment: pymol_2.2.0+dfsg-2.log.gz
Description: application/gzip

Reply via email to