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 like this: > > It looks like the definition of GLsizeiptr is different between the movit > and > nageru builds: > > > ./obj-mipsel-linux-gnu/../nageru/timecode_renderer.cpp:51: undefined > > reference > > to `movit::generate_vbo(int, unsigned int, long, void const*)' > > /usr/bin/ld: ./obj-mipsel-linux-gnu/../nageru/timecode_renderer.cpp:51: > > undefined reference to `movit::generate_vbo(int, unsigned int, long, void > > const*)' > > klump:~/dev/movit> nm --dynamic --demangle /usr/lib/i386-linux- > gnu/libmovit.so.8 | grep vbo > 0001b9a0 T movit::generate_vbo(int, unsigned int, int, void const*) > > Is this an ABI break caused by some recent Mesa change, perhaps? I guess one > could always rebuild Movit... > > Seemingly it changed upstream from ptrdiff_t to khronos_ssize_t in Nov 2018, > but I don't know if that was the actual break. krhonos_ssize_t is defined > as: > > typedef signed long int khronos_ssize_t;
In this case a rebuild might be worthwhile anyway. Rebuilding package is almost always harmless. Are you going to trigger the rebuild recently? If not, I can help to trigger it through NMU. -- Thanks, Boyuan Yang
