All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	"Lorenzati, Marcelo" <marcelo.lorenzati@intel.com>
Subject: Re: ulibc instead of glibc
Date: Tue, 25 Jan 2011 22:14:40 +0000	[thread overview]
Message-ID: <1295993680.27814.154.camel@rex> (raw)
In-Reply-To: <4D3F24FF.8050400@windriver.com>

On Tue, 2011-01-25 at 13:31 -0600, Mark Hatle wrote:
> On 1/25/11 12:36 PM, Lorenzati, Marcelo wrote:
> > Hi all,
> > 
> >                 I wanted to know if it’s feasible to build Yocto with ulibc
> > instead of glibc and if someone have tried.
> > 
> > In a really constrained system could be the difference between selecting RT
> > Linux or another real time OS.
> > 
> 
> So far uclibc has not been a goal of the Yocto project.  With the minimum size
> of flash parts these days, the configurability of eglibc and the mklibs library
> optimizer... the use-case for uclibc is quickly going away.
> 
> (eglibc configuration is not yet implemented in Yocto.  Mklibs is currently
> being implemented.)
> 
> We have built (at Wind River) eglibc filesystems, single application systems, in
> foot prints of less then 2 MB of disk space required.  As far as I know,
> currently the smallest flash parts you can get for new designs are in the 4 MB
> range, and quickly those are being replaced by 16 MB (and larger) parts...
> 
> eglibc also has the advantage (over uclibc) of better support for a wide range
> of existing Open Source projects.
> 
> With that all said, yes it should be feasible to add uclibc to Yocto... but it's
> not already there as far as I know.

Right, we do have old uclibc recipes in Poky still I believe although
they would need updating after the recent toolchain bootstrap changes. I
do know people using uclibc actively in OE and this may be something
people want to add to oe-core so it might end up happening but its not
currently on the officially supported by Yocto list. 

Cheers,

Richard




  reply	other threads:[~2011-01-25 22:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-25 18:36 ulibc instead of glibc Lorenzati, Marcelo
2011-01-25 19:31 ` Mark Hatle
2011-01-25 22:14   ` Richard Purdie [this message]
2011-01-26 21:30 ` Darren Hart
2011-01-27 12:31   ` Lorenzati, Marcelo

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=1295993680.27814.154.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --cc=marcelo.lorenzati@intel.com \
    --cc=mark.hatle@windriver.com \
    --cc=yocto@yoctoproject.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.