From: cern@tuta.io
To: Jan Kiszka <jan.kiszka@web.de>
Cc: 孙世龙 <sunshilong369@gmail.com>, xenomai <xenomai@xenomai.org>
Subject: Re: I think lib/copperplate depends on glibc while using dual kernel configuration.Am i right?
Date: Sat, 11 Apr 2020 18:45:17 +0200 (CEST) [thread overview]
Message-ID: <M4e7NsX--3-2@tuta.io> (raw)
In-Reply-To: <993ec258-fb69-cfa6-14f6-6cfb0967f9e8@web.de>
Hi,
Apr 11, 2020, 09:22 by xenomai@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.)
Cern.
>
> Jan
>
next prev parent reply other threads:[~2020-04-11 16:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 3:56 I think lib/copperplate depends on glibc while using dual kernel configuration.Am i right? 孙世龙
2020-04-11 7:22 ` Jan Kiszka
2020-04-11 16:45 ` cern [this message]
2020-04-11 17:52 ` Jan Kiszka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=M4e7NsX--3-2@tuta.io \
--to=cern@tuta.io \
--cc=jan.kiszka@web.de \
--cc=sunshilong369@gmail.com \
--cc=xenomai@xenomai.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.