From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] RT-Linux ucLibc or glibc?
Date: Thu, 22 Oct 2009 21:26:24 +0200 [thread overview]
Message-ID: <20091022212624.3dbe24ee@surf> (raw)
In-Reply-To: <B44D4D5BF344094DABB900C4E0F6E3533945A36BC5@srv02.nortechonline.net>
Le Wed, 21 Oct 2009 15:56:47 +0100,
"Hodgson, Simon" <Simon.Hodgson@nortechonline.co.uk> a ?crit :
> We're building a system, and want to make use of the RT-Preempt
> Kernel patch.
>
> My question is, do we need to use glibc, or will uClibc be OK?
>
> This wiki page suggests that some of the features required are not
> present in uclibc
> (http://rt.wiki.kernel.org/index.php/HOWTO:_Build_an_RT-application)
> but it was written some time ago.
>
> Just wondered if anyone has any experience of this?
Last time I looked, it was still the case. Things like
priority-inheritance mutexes for example were not supported.
Sincerly,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2009-10-22 19:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-21 14:56 [Buildroot] RT-Linux ucLibc or glibc? Hodgson, Simon
2009-10-22 19:26 ` Thomas Petazzoni [this message]
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=20091022212624.3dbe24ee@surf \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox