Struct included in two header files, neither of which I own

Question

I am trying to play with SCHED_DEADLINE in c++, I needed to send struct sched_attr to and ioctl so I included <linux/sched/types.h>, that header also happens to include strut sched_param. I also included <string> which includes the standard headers for c++ which eventually includes include\bits\sched.h which also defines struct sched_param. The compiler (obviously) doesn't particularly like this. I used the header guard (_BITS_TYPES_STRUCT_SCHED_PARAM) in my code to get the compiler to not include include\bits\sched.h, but it feels like there should be a "better" way.

> Executing task in folder sched_deadline_testing: arm-linux-gnueabihf-g++ -o LSM9DS0 src/LSM9DS0.cpp -Wall --pedantic <

In file included from src/LSM9DS0.cpp:36:
/usr/arm-linux-gnueabihf/include/linux/sched/types.h:7:8: error: redefinition of ‘struct sched_param’
 struct sched_param {
        ^~~~~~~~~~~
In file included from /usr/arm-linux-gnueabihf/include/bits/sched.h:74,
                 from /usr/arm-linux-gnueabihf/include/sched.h:43,
                 from /usr/arm-linux-gnueabihf/include/pthread.h:23,
                 from /usr/arm-linux-gnueabihf/include/c++/8/arm-linux-gnueabihf/bits/gthr-default.h:35,
                 from /usr/arm-linux-gnueabihf/include/c++/8/arm-linux-gnueabihf/bits/gthr.h:148,
                 from /usr/arm-linux-gnueabihf/include/c++/8/ext/atomicity.h:35,
                 from /usr/arm-linux-gnueabihf/include/c++/8/bits/basic_string.h:39,
                 from /usr/arm-linux-gnueabihf/include/c++/8/string:52,
                 from src/LSM9DS0.cpp:20:
/usr/arm-linux-gnueabihf/include/bits/types/struct_sched_param.h:23:8: note: previous definition of ‘struct sched_param’
 struct sched_param

The code is here if that's important. I have also tried this cross compiling, and compiling locally, both cause the issue.

463035818_is_not_an_ai · Accepted Answer · 2020-07-01 13:08:55Z

5

You're out of luck. The two headers are incompatible. You simply must avoid including both <linux/sched/types.h> and <string> into the same translation unit. It's probably worth noting that being a Linux kernel header, the former is probably not intended to be used in C++, nor has there been an attempt to make it compatible.

edited Jul 1, 2020 at 13:08

463035818_is_not_an_ai

128k11 gold badges114 silver badges239 bronze badges

answered Jul 1, 2020 at 13:05

eerorika

240k13 gold badges212 silver badges354 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

DevSolar Over a year ago

Actually making Linux headers C++ compatible has been actively opposed in the past by the ones in power. LKML FAQ 15.3. The argument being made is quite broken, but good luck changing their minds about it...

Collectives™ on Stack Overflow

Struct included in two header files, neither of which I own

1 Answer 1

1 Comment

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Related