The package failed to build on mips recently because some files
take way too long to compile and the build got killed due to inactivity:
[ 65%] Building CXX object gr-blocks/swig/CMakeFiles/_blocks_swig5.dir/blocks_swig5PYTHON_wrap.cxx.o
cd /«PKGBUILDDIR»/obj-mips-linux-gnu/gr-blocks/swig && /usr/bin/c++ -DENABLE_GR_LOG -DGR_PERFORMANCE_COUNTERS -DHAVE_LOG4CPP -D_blocks_swig5_EXPORTS -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -fvisibility=hidden -Wsign-compare -Wall -Wno-uninitialized -fPIC -I/«PKGBUILDDIR»/obj-mips-linux-gnu/gr-blocks/swig -I/«PKGBUILDDIR»/gr-blocks/swig -I/«PKGBUILDDIR»/gr-blocks/lib -I/«PKGBUILDDIR»/gr-blocks/include -I/«PKGBUILDDIR»/obj-mips-linux-gnu/gr-blocks/lib -I/«PKGBUILDDIR»/obj-mips-linux-gnu/gr-blocks/include -I/«PKGBUILDDIR»/obj-mips-linux-gnu -I/«PKGBUILDDIR»/gnuradio-runtime/include -I/«PKGBUILDDIR»/obj-mips-linux-gnu/gnuradio-runtime/include -I/«PKGBUILDDIR»/gnuradio-runtime/swig -I/«PKGBUILDDIR»/obj-mips-linux-gnu/gnuradio-runtime/swig -I/usr/include/python2.7 -Wno-unused-but-set-variable -o CMakeFiles/_blocks_swig5.dir/blocks_swig5PYTHON_wrap.cxx.o -c /«PKGBUILDDIR»/obj-mips-linux-gnu/gr-blocks/swig/blocks_sw
ig5PYTHON_wrap.cxx
E: Caught signal ‘Terminated’: terminating immediately
make[3]: *** [gr-blocks/swig/CMakeFiles/_blocks_swig4.dir/blocks_swig4PYTHON_wrap.cxx.o] Terminated
[...]
Build killed with signal TERM after 301 minutes of inactivity
See the build log here:
https://buildd.debian.org/status/fetch.php?pkg=gnuradio&arch=mips&ver=3.7.8-2.2&stamp=1441346704
I had this discussion on #debian-buildd:
15:16 <buxy> hum looks like https://buildd.debian.org/status/fetch.php?pkg=gnuradio&arch=mips&ver=3.7.8-2.2&stamp=1441346704 got "terminated" due to inactivity
15:17 <buxy> can it be rescheduled on a faster buildd or with a longer period? It's the only missing build of gnuradio
15:18 <jcristau> somebody should fix the package
15:18 <jcristau> to not need 5 hours to compile a single file
15:19 <buxy> p2-mate, aba: ^
15:19 <buxy> I can file such a bug but I don't think it's reasonable to impose this right now in particular when a single arch triggers it
15:20 <jcristau> *shrug*
15:22 <buxy> looks like it's generated wrapper code so it's probably not trivial to fix
I'm marking it as important as the package currently requires manual
hand-holding on the buildd side... if you know of a way to avoid this,
it would be nice to update the package.
Cheers,