From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Jussi Kukkonen <jussi.kukkonen@intel.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] linux-libc-headers: introduce 4.9 headers
Date: Sun, 25 Dec 2016 21:34:02 -0500 [thread overview]
Message-ID: <5860819A.4010109@windriver.com> (raw)
In-Reply-To: <CAHiDW_E+G1JAEODj3w6Xda4CJkjHGOnBB0h035p093ZGP7WTqA@mail.gmail.com>
On 16-12-23 5:23 AM, Jussi Kukkonen wrote:
> On 22 December 2016 at 16:49, Bruce Ashfield
> <bruce.ashfield@windriver.com <mailto:bruce.ashfield@windriver.com>> wrote:
> >
> > Bumping the linux-libc-headers to the 4.9 kernel variant. Since 4.9
> > will be a LTSI kernel, and there will be an associated linux-yocto
> > it is worth moving to these headers sooner rather than later.
> >
> > This commit also drops the 4.8 headers and sets 4.9 to be the default.
>
> The autobuilder run (ross/mut 1dc1894e05) with this had a couple of issues:
>
> *** ppp fails to build on musl:
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=10853
>
> *** ncurses fails in several builds, all gnu/stubs.h related:
> ncurses was also upgraded in this AB run (CCing Huang Qiyu) but the
> failures seem more like libc related...
>
> x32:
> |
> nightly-x32/build/build/tmp/sysroots/qemux86-64/usr/include/gnu/stubs.h:10:27:
> fatal error: gnu/stubs-64.h: No such file or directory
> | # include <gnu/stubs-64.h>
>
> arm:
> |
> nightly-arm/build/build/tmp/sysroots/beaglebone/usr/include/gnu/stubs.h:7:29:
> fatal error: gnu/stubs-soft.h: No such file or directory
> | # include <gnu/stubs-soft.h>
FYI: I was just able to build all variants on ncurses on the branches
I have available.
I'm going to need a bit more direction on what branch/config to build
to see this breakage.
Bruce
>
> multilib:
> |
> nightly-multilib/build/build/tmp/sysroots/qemumips64/usr/include/gnu/stubs.h:35:33:
> fatal error: gnu/stubs-n64_hard.h: No such file or directory
> | # include <gnu/stubs-n64_hard.h>
>
> The full build log links can be found in "nightly 1121" section here:
> https://wiki.yoctoproject.org/wiki/BuildLog#nightly_1121_-_ross.2Fmut_1dc1894e05ef0f3aeeefa61ed89613f17bba2e83
>
>
> Cheers,
> Jussi
next prev parent reply other threads:[~2016-12-26 2:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-22 14:49 [PATCH 0/2] kernel-yocto: 4.9 goodness Bruce Ashfield
2016-12-22 14:49 ` [PATCH 1/2] linux-libc-headers: introduce 4.9 headers Bruce Ashfield
2016-12-23 10:23 ` Jussi Kukkonen
2016-12-25 3:33 ` Bruce Ashfield
2016-12-26 2:34 ` Bruce Ashfield [this message]
2016-12-22 14:49 ` [PATCH 2/2] kernel: introduce linux-yocto v4.9 recipes Bruce Ashfield
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=5860819A.4010109@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=jussi.kukkonen@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox