Bug#838792: openmw: FTBFS on armhf: error: conflicting declaration for GLsizeiptr

2016-10-12 Thread bret curtis
Hello everyone, this is a follow-up email because while the bug was closed and OpenMW compiles (and runs) on armhf, what is rendered to the screen via OSG-3.4 is everything but pretty. The short term solution is to disable building OpenMW on armhf and rebuild any builds still online. I have more

Bug#838792: openmw: FTBFS on armhf: error: conflicting declaration for GLsizeiptr

2016-09-29 Thread Alberto Luaces
bret curtis writes: > With the attached patch to OSG, I can get it to compile on armhf with > GLESv1 (libgles1-mesa-dev). It disables GLESv2 however, I got an error > while they were both enabled. > > I installed the resulting packages on my RPi2 without a problem and > got OpenMW to compile on

Bug#838792: openmw: FTBFS on armhf: error: conflicting declaration for GLsizeiptr

2016-09-28 Thread bret curtis
With the attached patch to OSG, I can get it to compile on armhf with GLESv1 (libgles1-mesa-dev). It disables GLESv2 however, I got an error while they were both enabled. I installed the resulting packages on my RPi2 without a problem and got OpenMW to compile on there as well. Was there a

Bug#838792: openmw: FTBFS on armhf: error: conflicting declaration for GLsizeiptr

2016-09-28 Thread bret curtis
On Wed, Sep 28, 2016 at 9:34 AM, Alberto Luaces wrote: > Andreas Beckmann writes: > >> On 2016-09-27 12:12, bret curtis wrote: >>> To put it simply, upstream (OpenMW) has no plans to support GLESv2 at >>> this time. Since OSG-3.4 for armhf is compiled only for GLESv2, this >>>

Bug#838792: openmw: FTBFS on armhf: error: conflicting declaration for GLsizeiptr

2016-09-28 Thread Alberto Luaces
Andreas Beckmann writes: > On 2016-09-27 12:12, bret curtis wrote: >> To put it simply, upstream (OpenMW) has no plans to support GLESv2 at >> this time. Since OSG-3.4 for armhf is compiled only for GLESv2, this >> complicates things drastically and at this point I'm in over my head. > > IIRC,

Bug#838792: openmw: FTBFS on armhf: error: conflicting declaration for GLsizeiptr

2016-09-27 Thread Andreas Beckmann
On 2016-09-27 12:12, bret curtis wrote: > To put it simply, upstream (OpenMW) has no plans to support GLESv2 at > this time. Since OSG-3.4 for armhf is compiled only for GLESv2, this > complicates things drastically and at this point I'm in over my head. IIRC, quite some packages have been

Bug#838792: openmw: FTBFS on armhf: error: conflicting declaration for GLsizeiptr

2016-09-27 Thread bret curtis
Hello, To put it simply, upstream (OpenMW) has no plans to support GLESv2 at this time. Since OSG-3.4 for armhf is compiled only for GLESv2, this complicates things drastically and at this point I'm in over my head. If we try to switch out with , we clear up the above error but then it fails

Bug#838792: openmw: FTBFS on armhf: error: conflicting declaration for GLsizeiptr

2016-09-24 Thread bret curtis
We know what the problem is and are working on it. Please see the following: https://anonscm.debian.org/cgit/pkg-osg/openscenegraph-3.4.git/commit/?id=fa5b1385d2b82f3fec9cc6094fb3db498a36a9e3 OSG-3.4 had the same problem until this was commited, now the package builds and OpenMW was unblocked.

Bug#838792: openmw: FTBFS on armhf: error: conflicting declaration for GLsizeiptr

2016-09-24 Thread Andreas Beckmann
Package: openmw Version: 0.40.0-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, openmw/experimental FTBFS on armhf: https://buildd.debian.org/status/fetch.php?pkg=openmw=armhf=0.40.0-1=1474694818 In file included from