Merge lp:~gerboland/qtmir/xenial-armhf-fix into lp:qtmir
| Status: | Merged |
|---|---|
| Approved by: | Daniel d'Andrada on 2015-11-11 |
| Approved revision: | 405 |
| Merged at revision: | 407 |
| Proposed branch: | lp:~gerboland/qtmir/xenial-armhf-fix |
| Merge into: | lp:qtmir |
| Diff against target: |
11 lines (+1/-1) 1 file modified
CMakeLists.txt (+1/-1) |
| To merge this branch: | bzr merge lp:~gerboland/qtmir/xenial-armhf-fix |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| PS Jenkins bot | continuous-integration | Needs Fixing on 2015-11-11 | |
| Daniel d'Andrada (community) | 2015-11-11 | Approve on 2015-11-11 | |
|
Review via email:
|
|||
Commit Message
Fix armhf builds on Xenial by using -std=gnu99 instead of c99
Fixes this FTBFS on xenial:
In file included from /usr/include/
/usr/include/
/usr/include/
if (caa_unlikely(
^
/usr/include/
Strictly should compile code with -std=gnu99 instead of -std=c99 to have the identifiers SIGEV_SIGNAL, sigeventStruct, and CLOCK_MONOTONIC available. These identifiers are declared when _POSIX_C_SOURCE is set to a value >= 199309L, which is the case with -std=gnu99. I could also have used -D_POSIX_
Did not impact wily as libuctu only started looking for CLOCK_MONOTONIC in Xenial release.
Description of the Change
Strictly should compile code with -std=gnu99 instead of -std=c99 to have the identifiers SIGEV_SIGNAL, sigeventStruct, and CLOCK_MONOTONIC available. These identifiers are declared when _POSIX_C_SOURCE is set to a value >= 199309L, which is the case with -std=gnu99. I could also have used -D_POSIX_
| PS Jenkins bot (ps-jenkins) wrote : | # |
FAILED: Continuous integration, rev:405
http://
Executed test runs:
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
FAILURE: http://
FAILURE: http://
FAILURE: http://
Click here to trigger a rebuild:
http://

Alright