Bug 877689 – app-admin/ananicy-cpp-1.0.0_rc6-r1: error: flexible array member ‘cn_msg::data’ not at end of ‘struct set_event_subscription(int, bool)::nl_cn_msg’

• Status: RESOLVED OBSOLETE
• Product: GURU

[Description Lucas Rizzini 2022-10-19 20:23:06 UTC]

The build fails after setting ACCEPT_KEYWORDS="~amd64"

Reproducible: Always

Steps to Reproduce:
1. Emerge app-admin/ananicy-cpp-1.0.0_rc6-r1 after in a testing(~amd64) environment.
Actual Results:  
The build fails:
FAILED: CMakeFiles/ananicy-cpp.dir/src/platform/linux/process.cpp.o
/usr/bin/x86_64-pc-linux-gnu-g++ -DENABLE_SYSTEMD=1 -DFMT_SHARED -DSPDLOG_COMPILED_LIB -DSPDLOG_FMT_EXTERNAL -DSPDLOG_SHARED_LIB -I/usr/include/polyfills/format -I/var/tmp/portage/app-admin/ananicy-cpp-1.0.0_rc6-r1/work/ananicy-cpp-v1.0.0-rc6/include  -O2 -pipe -march=native -g -g3 -g3 -std=gnu++20 -MD -MT CMakeFiles/ananicy-cpp.dir/src/platform/linux/process.cpp.o -MF CMakeFiles/ananicy-cpp.dir/src/platform/linux/process.cpp.o.d -o CMakeFiles/ananicy-cpp.dir/src/platform/linux/process.cpp.o -c /var/tmp/portage/app-admin/ananicy-cpp-1.0.0_rc6-r1/work/ananicy-cpp-v1.0.0-rc6/src/platform/linux/process.cpp
In file included from /var/tmp/portage/app-admin/ananicy-cpp-1.0.0_rc6-r1/work/ananicy-cpp-v1.0.0-rc6/src/platform/linux/process.cpp:14:
/usr/include/linux/connector.h: In function ‘int set_event_subscription(int, bool)’:
/usr/include/linux/connector.h:78:14: error: flexible array member ‘cn_msg::data’ not at end of ‘struct set_event_subscription(int, bool)::nl_cn_msg’
   78 |         __u8 data[];
      |              ^~~~
/var/tmp/portage/app-admin/ananicy-cpp-1.0.0_rc6-r1/work/ananicy-cpp-v1.0.0-rc6/src/platform/linux/process.cpp:64:29: note: next member ‘proc_cn_mcast_op set_event_subscription(int, bool)::nl_cn_msg::<unnamed struct>::cn_mcast’ declared here
   64 |       enum proc_cn_mcast_op cn_mcast;
      |                             ^~~~~~~~
/var/tmp/portage/app-admin/ananicy-cpp-1.0.0_rc6-r1/work/ananicy-cpp-v1.0.0-rc6/src/platform/linux/process.cpp:60:33: note: in the definition of ‘struct set_event_subscription(int, bool)::nl_cn_msg’
   60 |   struct alignas(NLMSG_ALIGNTO) nl_cn_msg {
      |                                 ^~~~~~~~~
/usr/include/linux/connector.h: In function ‘int handle_events(int, synchronized_queue<Process>*, const std::stop_token&)’:
/usr/include/linux/connector.h:78:14: error: flexible array member ‘cn_msg::data’ not at end of ‘struct handle_events(int, synchronized_queue<Process>*, const std::stop_token&)::nl_cn_msg’
   78 |         __u8 data[];
      |              ^~~~
/var/tmp/portage/app-admin/ananicy-cpp-1.0.0_rc6-r1/work/ananicy-cpp-v1.0.0-rc6/src/platform/linux/process.cpp:94:25: note: next member ‘proc_event handle_events(int, synchronized_queue<Process>*, const std::stop_token&)::nl_cn_msg::<unnamed struct>::proc_ev’ declared here
   94 |       struct proc_event proc_ev;
      |                         ^~~~~~~
/var/tmp/portage/app-admin/ananicy-cpp-1.0.0_rc6-r1/work/ananicy-cpp-v1.0.0-rc6/src/platform/linux/process.cpp:90:33: note: in the definition of ‘struct handle_events(int, synchronized_queue<Process>*, const std::stop_token&)::nl_cn_msg’
   90 |   struct alignas(NLMSG_ALIGNTO) nl_cn_msg {
      |                                 ^~~~~~~~~


I created an issue on their Gitlab: https://gitlab.com/ananicy-cpp/ananicy-cpp/-/issues/47

[Comment 1 Lucas Rizzini 2022-10-19 20:23:36 UTC]

Created attachment 824811 [details]
Full log

[Comment 2 Sam James 2022-10-20 04:01:31 UTC]

Yeah, a linux-headers-6.0 issue.

[Comment 3 Lucas Rizzini 2022-10-26 15:21:59 UTC]

*** Bug 878377 has been marked as a duplicate of this bug. ***

[Comment 4 Alberto Gireud 2024-03-26 23:56:15 UTC]

From the conversation upstream and previous comments it seems this issue was related to changes in linux-headers-6.0.

Given this bug was originally opened against the 1.0.0_rc6 version and I am unable to reproduce the build failure for 1.1.1-r3 on a stable 6.6.21 kernel, I will be resolving this bug in a couple of weeks unless further information can be provided on how to reproduce the issue on the latest version.