All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Seth Bollinger <seth.boll@gmail.com>
Cc: Yocto discussion list <yocto@yoctoproject.org>,
	openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] OpenEmbedded and musl-libc
Date: Wed, 26 Mar 2014 17:44:20 +0100	[thread overview]
Message-ID: <20140326174420.648506cf@skate> (raw)
In-Reply-To: <CA+JN8xOH+=oJe3w_e06q3VJqZ9T_mQdmbUK8CBL3RE9+h=BiUQ@mail.gmail.com>

Dear Seth Bollinger,

On Fri, 21 Mar 2014 08:26:08 -0500, Seth Bollinger wrote:

> > I saw that yesterday too and thought it could be interesting for
> > Yocto.  I'm curious as to why it's better than uclibc though
> > (genuinely curious, I know little about uclibc beyond "it's smaller").
> 
> It been a while since I've reviewed uclibc, but doesn't it break a lot of
> software with its vfork only paradigm?

I'm not sure where you have seen that uClibc has vfork() only paradigm,
but it's not correct. uClibc has a proper fork() implementation on all
MMU-equipped CPU architectures that uClibc support. Only the non-MMU
architectures are limited to vfork(). The originality of uClibc here is
probably precisely the fact that it supports non-MMU architectures,
which many other C libraries do not.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com


  reply	other threads:[~2014-03-26 16:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-21 12:34 OpenEmbedded and musl-libc Paul Barker
2014-03-21 13:10 ` [OE-core] " Burton, Ross
2014-03-21 13:10   ` Burton, Ross
2014-03-21 13:26   ` [OE-core] " Seth Bollinger
2014-03-21 13:26     ` [yocto] " Seth Bollinger
2014-03-26 16:44     ` Thomas Petazzoni [this message]
2014-03-21 14:37   ` [OE-core] " Paul Barker
2014-03-21 14:37     ` Paul Barker
2014-03-26 16:46     ` [OE-core] " Thomas Petazzoni
2014-03-21 13:42 ` Kevyn-Alexandre Paré
2014-03-21 16:16   ` Kevyn-Alexandre Paré
2014-03-21 18:22 ` [OE-core] " Khem Raj
2014-03-21 18:22   ` Khem Raj
2014-03-21 19:41   ` [OE-core] " Paul Barker
2014-03-21 19:41     ` Paul Barker
2014-03-26 16:48   ` [OE-core] " Thomas Petazzoni
2014-03-26 21:49     ` Khem Raj
2014-03-26 21:49       ` [yocto] " Khem Raj

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=20140326174420.648506cf@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=seth.boll@gmail.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.