Hmm, why don't you poke the person who's responsible for the packaging with this, to adjust the build script in a matter of passing different cflags if using armv7 and trusty? I'm not really keen on setting up a specific chroot for trusty, mostly because I have a limited internet connection. The compile is not that much of a burden, for 59.0 it takes 10 hours on a rpi2 with -j2 and a bit of swapping, as non debug build. Can be done overnight.
Clang is more memory efficent, so you can pass -j4 on the rpi2 quadcore and swap a bit here and there, the built would be a little bit faster this way and might allow to workaround the segfault. But again Ubuntu doesn't have >=clang-4 for armhf and trusty available, does it?
Hmm, why don't you poke the person who's responsible for the packaging with this, to adjust the build script in a matter of passing different cflags if using armv7 and trusty? I'm not really keen on setting up a specific chroot for trusty, mostly because I have a limited internet connection. The compile is not that much of a burden, for 59.0 it takes 10 hours on a rpi2 with -j2 and a bit of swapping, as non debug build. Can be done overnight.
Clang is more memory efficent, so you can pass -j4 on the rpi2 quadcore and swap a bit here and there, the built would be a little bit faster this way and might allow to workaround the segfault. But again Ubuntu doesn't have >=clang-4 for armhf and trusty available, does it?