All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.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 14:49:28 -0700	[thread overview]
Message-ID: <CAMKF1spF7x8qnnCtBAzbf_knWSJ9roa-RkqdscBLLhKH_JqV8g@mail.gmail.com> (raw)
In-Reply-To: <20140326174829.5d897f11@skate>

On Wed, Mar 26, 2014 at 9:48 AM, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
> Dear Khem Raj,
>
> On Fri, 21 Mar 2014 11:22:24 -0700, Khem Raj wrote:
>
>> it has been under my radar for a while. I have actually locally made
>> toolchains with
>> clang+musl and it seems to be coming along. its licensed differently thats
>> the biggest attraction for folks who do static linking. Otherwise it still
>> doesnt yet support variety of architectures that other libcs support. given
>> now we have kconfig for eglibc too may be it fills in the nommu gap much
>> like uclibc does today.
>
> The non-MMU gap? Last time I looked, musl didn't had support for any
> non-MMU architecture.

yes it does not. I meant to state the reverse that mmu-less systems is
where uclibc will have edge left.


WARNING: multiple messages have this Message-ID (diff)
From: Khem Raj <raj.khem@gmail.com>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Yocto discussion list <yocto@yoctoproject.org>,
	openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [yocto] OpenEmbedded and musl-libc
Date: Wed, 26 Mar 2014 14:49:28 -0700	[thread overview]
Message-ID: <CAMKF1spF7x8qnnCtBAzbf_knWSJ9roa-RkqdscBLLhKH_JqV8g@mail.gmail.com> (raw)
In-Reply-To: <20140326174829.5d897f11@skate>

On Wed, Mar 26, 2014 at 9:48 AM, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
> Dear Khem Raj,
>
> On Fri, 21 Mar 2014 11:22:24 -0700, Khem Raj wrote:
>
>> it has been under my radar for a while. I have actually locally made
>> toolchains with
>> clang+musl and it seems to be coming along. its licensed differently thats
>> the biggest attraction for folks who do static linking. Otherwise it still
>> doesnt yet support variety of architectures that other libcs support. given
>> now we have kconfig for eglibc too may be it fills in the nommu gap much
>> like uclibc does today.
>
> The non-MMU gap? Last time I looked, musl didn't had support for any
> non-MMU architecture.

yes it does not. I meant to state the reverse that mmu-less systems is
where uclibc will have edge left.


  reply	other threads:[~2014-03-26 21:49 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     ` [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 [this message]
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=CAMKF1spF7x8qnnCtBAzbf_knWSJ9roa-RkqdscBLLhKH_JqV8g@mail.gmail.com \
    --to=raj.khem@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=thomas.petazzoni@free-electrons.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.