From: Seth Bollinger <seth.boll@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Yocto discussion list <yocto@yoctoproject.org>,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] OpenEmbedded and musl-libc
Date: Fri, 21 Mar 2014 08:26:08 -0500 [thread overview]
Message-ID: <CA+JN8xOH+=oJe3w_e06q3VJqZ9T_mQdmbUK8CBL3RE9+h=BiUQ@mail.gmail.com> (raw)
In-Reply-To: <CAJTo0Las0o_JcsvW-X+L=EQAvUf3yVVQBunoCi=cAzR=3y2DrA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 340 bytes --]
>
>
> 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?
Seth
[-- Attachment #2: Type: text/html, Size: 620 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Seth Bollinger <seth.boll@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Yocto discussion list <yocto@yoctoproject.org>,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [yocto] OpenEmbedded and musl-libc
Date: Fri, 21 Mar 2014 08:26:08 -0500 [thread overview]
Message-ID: <CA+JN8xOH+=oJe3w_e06q3VJqZ9T_mQdmbUK8CBL3RE9+h=BiUQ@mail.gmail.com> (raw)
In-Reply-To: <CAJTo0Las0o_JcsvW-X+L=EQAvUf3yVVQBunoCi=cAzR=3y2DrA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 340 bytes --]
>
>
> 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?
Seth
[-- Attachment #2: Type: text/html, Size: 620 bytes --]
next prev parent reply other threads:[~2014-03-21 13:26 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 ` Seth Bollinger [this message]
2014-03-21 13:26 ` [yocto] " Seth Bollinger
2014-03-26 16:44 ` [OE-core] " Thomas Petazzoni
2014-03-21 14:37 ` 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='CA+JN8xOH+=oJe3w_e06q3VJqZ9T_mQdmbUK8CBL3RE9+h=BiUQ@mail.gmail.com' \
--to=seth.boll@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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.