From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Bruce Ashfield <bruce.ashfield@windriver.com>,
Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
Saul Wold <saul.wold@intel.com>
Subject: Re: [PATCH 8/8] linux-yocto-dev: update to v4.15+
Date: Mon, 04 Dec 2017 17:39:39 +0000 [thread overview]
Message-ID: <1512409179.862.212.camel@linuxfoundation.org> (raw)
In-Reply-To: <ad367df7-795c-20c9-eef3-436f12038f97@windriver.com>
On Mon, 2017-12-04 at 12:24 -0500, Bruce Ashfield wrote:
> On 2017-12-04 11:38 AM, Khem Raj wrote:
> >
> > On Mon, Dec 4, 2017 at 7:39 AM, Bruce Ashfield
> > <bruce.ashfield@windriver.com> wrote:
> > >
> > > Outside of the normal patch refreshes and boot issues, there are
> > > new
> > > build time tools within the kernel that required the following
> > > dependencies:
> > >
> > > For ORC_UNWINDER support in x86-64:
> > >
> > > DEPENDS += "${@bb.utils.contains('ARCH', 'x86', 'elfutils-
> > > native elfutils', '', d)}"
> > do we need both target and host elfutils
> Yup. There were references to both. Some had to run for hostcc
> and others in the target arch.
Just for reference this is pretty bad for performance as it delays the
kernel compile until some substantial parts of userspace build.
Is ORC_UNWINDER useful and commonly used?
Cheers,
Richard
next prev parent reply other threads:[~2017-12-04 17:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 15:39 [PATCH 0/8] kernel-yocto: consolidated pull request Bruce Ashfield
2017-12-04 15:39 ` [PATCH 1/8] linux-yocto/4.9: update to v4.9.61 Bruce Ashfield
2017-12-04 15:39 ` [PATCH 2/8] linux-yocto/4.12: iwlwifi calltrace fixes and configuration warning cleanups Bruce Ashfield
2017-12-04 15:39 ` [PATCH 3/8] linux-yocto/4.9: update to v4.9.65 Bruce Ashfield
2017-12-04 15:39 ` [PATCH 4/8] linux-yocto/4.12: update to v4.12.16 Bruce Ashfield
2017-12-05 16:26 ` akuster808
2017-12-05 19:17 ` Bruce Ashfield
2017-12-04 15:39 ` [PATCH 5/8] kernel-yocto: ensure sccs variable is set when using KBUILD_DEFCONFIG Bruce Ashfield
2017-12-04 15:39 ` [PATCH 6/8] kernel-yocto: Stop the build if defconfig is missing Bruce Ashfield
2017-12-04 15:39 ` [PATCH 7/8] kernel-yocto: ensure that only a single defconfig is processed Bruce Ashfield
2017-12-04 15:39 ` [PATCH 8/8] linux-yocto-dev: update to v4.15+ Bruce Ashfield
2017-12-04 16:38 ` Khem Raj
2017-12-04 17:24 ` Bruce Ashfield
2017-12-04 17:39 ` Richard Purdie [this message]
2017-12-04 17:43 ` Bruce Ashfield
2017-12-06 16:28 ` Burton, Ross
2017-12-07 10:30 ` Bruce Ashfield
2017-12-07 15:36 ` Wold, Saul
2017-12-04 17:46 ` Bruce Ashfield
2017-12-10 12:32 ` [PATCH 0/8] kernel-yocto: consolidated pull request Richard Purdie
2017-12-10 15:16 ` Bruce Ashfield
2017-12-10 17:40 ` Bruce Ashfield
2017-12-10 17:44 ` 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=1512409179.862.212.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=saul.wold@intel.com \
/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