Bug#949264: nageru: FTBFS on arm/i386/mipsel architectures

2020-01-20 Thread Steinar H. Gunderson
On Mon, Jan 20, 2020 at 04:32:14PM -0500, Boyuan Yang wrote: > In this case a rebuild might be worthwhile anyway. Rebuilding package is > almost always harmless. Well, rebuilding movit would fix it, but it would also break any reverse dependency, so they would also need to be rebuilt. And if my

Bug#949264: nageru: FTBFS on arm/i386/mipsel architectures

2020-01-20 Thread Boyuan Yang
Hi, 在 2020-01-19日的 10:38 +0100,Steinar H. Gunderson写道: > On Sun, Jan 19, 2020 at 12:50:43AM -0500, Boyuan Yang wrote: > > Recent source-only rebuild for nageru has mulitple FTBFS architectures on > > buildd: https://buildd.debian.org/status/package.php?p=nageru > > > > The tail log all reads

Bug#949264: nageru: FTBFS on arm/i386/mipsel architectures

2020-01-19 Thread Steinar H. Gunderson
On Sun, Jan 19, 2020 at 12:50:43AM -0500, Boyuan Yang wrote: > Recent source-only rebuild for nageru has mulitple FTBFS architectures on > buildd: https://buildd.debian.org/status/package.php?p=nageru > > The tail log all reads like this: It looks like the definition of GLsizeiptr is different

Bug#949264: nageru: FTBFS on arm/i386/mipsel architectures

2020-01-18 Thread Boyuan Yang
Package: nageru Severity: serious Version: 1.9.1-1.1 Recent source-only rebuild for nageru has mulitple FTBFS architectures on buildd: https://buildd.debian.org/status/package.php?p=nageru The tail log all reads like this: /usr/bin/ld: libcore.a(nageru_timecode_renderer.cpp.o): in function