From: Khem Raj <raj.khem@gmail.com> To: Paul Barker <paul@paulbarker.me.uk> 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 11:22:24 -0700 [thread overview] Message-ID: <CAMKF1sq7QUcKypgyn8auurnqRd5ZfztdymcxquRwsRxvN4seqw@mail.gmail.com> (raw) In-Reply-To: <CANyK_8e6dfzu64SRLzZdXFE3obT6Td-8UUDqfcoSAqWTjoOq3g@mail.gmail.com> On Fri, Mar 21, 2014 at 5:34 AM, Paul Barker <paul@paulbarker.me.uk> wrote: > Hi all, > > musl-libc hit version 1.0.0 yesterday and is starting to look good to > me. It's basically a really small but very functional libc that would > suit embedded environments very well as an alternative to > eglibc/uclibc. I'm personally very interested in using it in my > projects and I also think it could fit in well with the aims of > poky-tiny. > > http://www.etalabs.net/compare_libcs.html gives some pretty useful info. > > I'm basically emailing to see if anyone else is interested in this or > if anyone has looked at using it before in OpenEmbedded as a google > for previous discussions didn't turn anything up. > > I'm currently very busy between various projects so I don't have time > to hack together a musl-libc recipe myself but I should have time to > help test it. 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. I have some plans for 1.7 for adding it to OE may be in a layer of its own first and then migrate it to OE-core > > Thanks, > > -- > Paul Barker > > Email: paul@paulbarker.me.uk > http://www.paulbarker.me.uk > -- > _______________________________________________ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core
WARNING: multiple messages have this Message-ID (diff)
From: Khem Raj <raj.khem@gmail.com> To: Paul Barker <paul@paulbarker.me.uk> Cc: Yocto discussion list <yocto@yoctoproject.org>, openembedded-core <openembedded-core@lists.openembedded.org> Subject: Re: OpenEmbedded and musl-libc Date: Fri, 21 Mar 2014 11:22:24 -0700 [thread overview] Message-ID: <CAMKF1sq7QUcKypgyn8auurnqRd5ZfztdymcxquRwsRxvN4seqw@mail.gmail.com> (raw) In-Reply-To: <CANyK_8e6dfzu64SRLzZdXFE3obT6Td-8UUDqfcoSAqWTjoOq3g@mail.gmail.com> On Fri, Mar 21, 2014 at 5:34 AM, Paul Barker <paul@paulbarker.me.uk> wrote: > Hi all, > > musl-libc hit version 1.0.0 yesterday and is starting to look good to > me. It's basically a really small but very functional libc that would > suit embedded environments very well as an alternative to > eglibc/uclibc. I'm personally very interested in using it in my > projects and I also think it could fit in well with the aims of > poky-tiny. > > http://www.etalabs.net/compare_libcs.html gives some pretty useful info. > > I'm basically emailing to see if anyone else is interested in this or > if anyone has looked at using it before in OpenEmbedded as a google > for previous discussions didn't turn anything up. > > I'm currently very busy between various projects so I don't have time > to hack together a musl-libc recipe myself but I should have time to > help test it. 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. I have some plans for 1.7 for adding it to OE may be in a layer of its own first and then migrate it to OE-core > > Thanks, > > -- > Paul Barker > > Email: paul@paulbarker.me.uk > http://www.paulbarker.me.uk > -- > _______________________________________________ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2014-03-21 18:22 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 ` Khem Raj [this message] 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=CAMKF1sq7QUcKypgyn8auurnqRd5ZfztdymcxquRwsRxvN4seqw@mail.gmail.com \ --to=raj.khem@gmail.com \ --cc=openembedded-core@lists.openembedded.org \ --cc=paul@paulbarker.me.uk \ --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: linkBe 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.