IPC error 2: semget: Function not implemented
We are having problems with running our C++ application on the AXC F 2152. A library (RTI Connext DDS) we depend on is calling semget, which is failing with ENOSYS (Function not implemented).
Our guess is that either the libc on device does not have an implementation for semget, or the Linux kernel was built without the appropriate configuration option (CONFIG_SYSVIPC, I think).
Comments
Hi Mathias,
Was the RTI Connext DDS library built using a PLCnext SDK? Or perhaps it was built with a generic armv7hf toolchain?
I would like to try and reproduce the error here. Can you give me more information on where to get the RTI Connext DDS library, and a minimum working example of code that causes the problem?
Martin.
Hello,
The RTI libs are not built using the SDK, however, we have already tested to compile a small example to verify that the problem is not related only to RTI libs.
When we built our own small test application with your SDK we got the same result.
I was not able to attach the files directly here, so you can download the example code we used here: https://paste.crimson.no/09F88D74C5B274D92BFEAF2D43BCC374.cpp
The example was derived from the semget documentation: https://pubs.opengroup.org/onlinepubs/009695399/functions/semget.html
Hi Mathias,
Just letting you know that we're still looking at this here, and someone will be back to you when we have a result (and hopefully a solution).
Martin.
Hi Mathias,
Sorry for the delay.
Our firmware dev team have investigated this and, as you suspected, it is a kernel setting that is stopping this from working.
We are quite keen to make this work, so we are looking at the options of how best to get a version of firmware that will solve this problem.
I do not have a timeframe at the moment, but we will keep you updated on progress. In the mean time, please let me know if you have any other questions.
Martin.
Martin,
I am experiencing this same issue with RTI's DDS implementation on the AXC F 2152. Is a solution still actively being pursued?
edit: Actually, I'm looking at the release notes for firmware version 2020.0 LTS, and I see a section called "Implementation of the 'SysV IPC' Linux extension." It sounds like this issue was addressed. I'll have to try updating my firmware to see if my issue is resolved.
Patrick
Hi Patrick,
Yes, we have a solution for this issue. Please drop me an email (mboers at phoenixcontact dot com) and I will put you in touch with the right people here.
~ Martin.