On Tue, Jan 05, 2016 at 11:44:51AM -0300, Lisandro Damián Nicanor Pérez Meyer wrote: > I'm tempted to remove libqt5gui5 from the list of packages that hold this > bug. > It is not a bug at all from our side, arm* uses GLES (except arm64 for now) > and GLU is not ported to it.
i do see qt (in whichever package) as being the "culprit" in this situation: gl and gles being incompatible is something that at least seems to be well-established. qt, on the other hand, used to work on well on armhf for openscad users (#797816), which now suffer a regression, and start suggesting to go back to qt4 where things worked perfectly. as far as i can judge, the choice of gles for qt builds on arm comes from *most* arm boards having gles support (only?). unless libqt5gui5 resolves this by building a gl and a gles version (or libglew stops conflicting against libgles, which seems to be more of an upstream than a packaging issue, but justifies the bug being assigned to those three packages), no non-gles qt programs can be used on those arm devices where they would have previously worked. (of course, those never worked on gles, but that's their individual or a glew/gles issue). best regards chrysn
signature.asc
Description: PGP signature
