[Bug 1527741] Re: oxide-qt 1.11.3-0ubuntu2 FTBFS on armhf due to compiler segfault

[Olivier Tilloy]

The latest successful build of oxide on xenial was done on the 5th of
December, against gcc 5.2.1-27ubuntu1.1. Xenial now has gcc
5.3.1-4ubuntu1, so there’s no going back to 5.2, we are gonna need to
figure out how to build oxide against 5.3.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to gcc-5 in Ubuntu.
https://bugs.launchpad.net/bugs/1527741

Title:
  oxide-qt 1.11.3-0ubuntu2 FTBFS on armhf due to compiler segfault

Status in gcc-5 package in Ubuntu:
  Fix Released
Status in oxide-qt package in Ubuntu:
  New

Bug description:
  We tried doing a no-change rebuild of oxide-qt 1.11.3-0ubuntu1
  (versioned as 1.11.3-0ubuntu2) and the build failed on armhf only. The
  reason is a compiler segfault:

  In file included from ../../../../third_party/chromium/src/third_party/webrtc/common_audio/signal_processing/downsample_fast_neon.c:13:0:
  /usr/lib/gcc/arm-linux-gnueabihf/5/include/arm_neon.h: In function 'WebRtcSpl_DownsampleFastNeon':
  /usr/lib/gcc/arm-linux-gnueabihf/5/include/arm_neon.h:6831:10: internal compiler error: Segmentation fault
  (...)

  Full log and build link here: https://launchpad.net/ubuntu/+source
  /oxide-qt/1.11.3-0ubuntu2/+build/8458995

  Looks like the previous oxide-qt successfully built version was built
  against gcc 5.2.1 while this time gcc 5.3.1 is used.

  This is critical for us to fix as multiple Ubuntu Touch landings are
  now blocked due to LP: #1527544 - and the no-change rebuild is
  required to fix the broken situation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-5/+bug/1527741/+subscriptions