oxide-qt 1.11.3-0ubuntu2 FTBFS on armhf due to compiler segfault
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gcc-5 (Ubuntu) |
Fix Released
|
Critical
|
Unassigned |
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 ../../.
/usr/lib/
/usr/lib/
(...)
Full log and build link here: https:/
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.
Changed in oxide-qt (Ubuntu): | |
status: | New → Confirmed |
Changed in gcc-5 (Ubuntu): | |
importance: | Undecided → Critical |
no longer affects: | oxide-qt (Ubuntu) |
this is not reproducible on the porter boxes. Please could you point me to a reproducer on a porter box?
and why do you file a bug report against gcc-5-cross when reporting an issue with the native compiler?