Actions
Bug #5004
closedMore fallout from -std=gnu11 on debian8
Start date:
02/02/2021
Due date:
% Done:
100%
Spec Reference:
Description
After libosmocore is fixed (#4991), osmo-bts and libosmo-sccp are failing with similar "error: initializer element is not constant" errors.
I'll fix it and verify that all packages build for debian8 now, as we might get that with other packages as well.
Related issues
Updated by osmith about 3 years ago
- Related to Bug #4991: fails to build on OBS/debian 8 added
Updated by osmith about 3 years ago
libosmo-sccp fails with:
[ 173s] CC xua_test.o [ 173s] In file included from ../../include/../src/xua_internal.h:4:0, [ 173s] from xua_test.c:21: [ 173s] ../../include/osmocom/sigtran/xua_msg.h:25:39: error: initializer element is not constant [ 173s] #define XUA_HDR(class, type) ((struct xua_common_hdr) { .spare = 0, .msg_class = (class), .msg_type = (type) }) [ 173s] ^ [ 173s] xua_test.c:387:11: note: in expansion of macro 'XUA_HDR' [ 173s] .hdr = XUA_HDR(SUA_MSGC_CL, SUA_CL_CLDT), [ 173s] ^ [ 173s] ../../include/osmocom/sigtran/xua_msg.h:25:39: error: (near initialization for 'sccp2sua_testcases[0].sua.hdr') [ 173s] #define XUA_HDR(class, type) ((struct xua_common_hdr) { .spare = 0, .msg_class = (class), .msg_type = (type) }) [ 173s] ^ [ 173s] xua_test.c:387:11: note: in expansion of macro 'XUA_HDR' [ 173s] .hdr = XUA_HDR(SUA_MSGC_CL, SUA_CL_CLDT), [ 173s] ^ [ 173s] Makefile:381: recipe for target 'xua_test.o' failed
osmo-bts fails with:
[ 167s] CC measurement.o [ 167s] measurement.c:33:1: error: initializer element is not constant [ 167s] }; [ 167s] ^
Updated by osmith about 3 years ago
- % Done changed from 0 to 20
Related patches:
https://gerrit.osmocom.org/q/topic:cstd+status:open
Updated by laforge about 3 years ago
maybe c11 was a bit too new, after all. I explicitly commented on that, but then
stated "ok" as it was generally understood that C11 is supported everywhere :P
Updated by osmith about 3 years ago
- % Done changed from 20 to 90
Well, the good news is that there are no more failures besides the libosmocore osmo-bts and libosmo-sccp errors.
I'll update the libosmo-sccp patch and test it again.
Updated by osmith about 3 years ago
- Status changed from In Progress to Resolved
- % Done changed from 90 to 100
Actions