I think lib/copperplate depends on glibc while using dual kernel configuration.Am i right?

Jan Kiszka jan.kiszka at web.de
Sat Apr 11 19:52:08 CEST 2020

On 11.04.20 18:45, cern at tuta.io wrote:
> Hi,
> Apr 11, 2020, 09:22 by xenomai at xenomai.org:
>> On 10.04.20 05:56, 孙世龙 via Xenomai wrote:
>>> Hi,
>>>   I am using xenomai-3.1.
>>>   Two figures are contained in url
>>> https://gitlab.denx.de/Xenomai/xenomai/-/wikis/Start_Here.
>>>   Since the architecture showed in figure 2 named xenomai 3 single kernel
>>> configuration, i could draw the conclusion that copperplate interface
>>> depends on the glibc.
>>>   But i don't think i can draw the same conclusion from the Figure 1.
>>> Xenomai 3 dual kernel configuration.
>>>   When i enable the --enable-pshared compiler option, I could clearlly see
>>> the create_main_heap function calls shm_open which is provided by glibc.
>>>   So, i think copperplate interface depends on glibc while using dual
>>> kernel configuration.Am i right?
>> Xenomai does not replace a libc when using the cobalt mode. It only
>> provides alternatives to certain time-sensitive services. So a libc,
>> like glibc, remains a natural dependency, for Xenomai libs themselves as
>> well as the target application.
> What about musl or other libc interpretations? (I haven't tried it yet, it's in my plan.)

It should work, but I didn't try myself. We have uclibc running, at
least on some arch.


More information about the Xenomai mailing list