From: Khem Raj <raj.khem@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 00/80] Consolidated pull
Date: Fri, 13 Jan 2017 09:14:42 -0800 [thread overview]
Message-ID: <35e72a1e-a77a-ee73-cd8b-7ee62db7ddd4@gmail.com> (raw)
In-Reply-To: <CAJTo0LZcdu=N99Brb5zocN9w2cROjDU6dgT-1HwXvkJKpxe6cw@mail.gmail.com>
On 1/13/17 6:25 AM, Burton, Ross wrote:
>
> On 13 January 2017 at 14:19, Bruce Ashfield <bruce.ashfield@gmail.com
> <mailto:bruce.ashfield@gmail.com>> wrote:
>
> I'm not much good with musl unfortunately, but honestly, I'm
> wondering how long we
> can keep this out with relatively few build issues. In tree, they'll
> get more attention.
>
>
> This is a greater problem - the kernel guys seem to think that glibc is
> the only C library worth thinking about. Khem took the action to talk
> with musl and get their headers fixed - which I believe is just adding a
> new #define to them.
There is an idea to preprocess the kernel headers for musl systems, I
will replicate whatever action community decides on.
>
> I'll continue stacking on 4.9 changes until they get sorted out.
> I'll probably have some
> cycles near the end of next week to get lost in c library #ifdef's,
> if the issues are still
> around.
>
>
> I keep on pushing the kernel bits to mut2, so feel free to send an
> updated branch and I can merge that in too.
>
> Ross
>
>
next prev parent reply other threads:[~2017-01-13 17:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 13:00 [PATCH 00/80] Consolidated pull Ross Burton
2017-01-13 13:16 ` Burton, Ross
2017-01-13 13:39 ` Bruce Ashfield
2017-01-13 14:16 ` Jussi Kukkonen
2017-01-13 14:19 ` Bruce Ashfield
2017-01-13 14:25 ` Burton, Ross
2017-01-13 14:29 ` Bruce Ashfield
2017-01-13 14:32 ` Bruce Ashfield
2017-01-13 14:37 ` Burton, Ross
2017-01-13 17:14 ` Khem Raj [this message]
2017-01-13 15:09 ` Burton, Ross
2017-01-13 15:13 ` Burton, Ross
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=35e72a1e-a77a-ee73-cd8b-7ee62db7ddd4@gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-core@lists.openembedded.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.