From: "Hart, Darren" <darren.hart@intel.com>
To: "Ashfield, Bruce (Wind River)" <bruce.ashfield@windriver.com>,
"Richard Purdie" <richard.purdie@linuxfoundation.org>,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] image: Add missing depends on virtual/kernel for depmod data
Date: Tue, 27 Jan 2015 15:48:02 +0000 [thread overview]
Message-ID: <D0ECF2E2.B9709%darren.hart@intel.com> (raw)
In-Reply-To: <54C7B296.5020506@windriver.com>
On 1/27/15, 7:45 AM, "Bruce Ashfield" <bruce.ashfield@windriver.com> wrote:
>On 15-01-27 10:29 AM, Richard Purdie wrote:
>> We need the depmod data so that the kernel depmod command works
>>successfully
>> at rootfs time. The fact this was working inconsistently is now
>>highlighted
>> after the command was made to error out. A simple test case is:
>>
>> bitbake virtual/kernel image
>> bitbake vrituak/kernel -c clean
>> bitbake image -c rootfs -f
>>
>> We fix it by adding the missing dependency.
>
>Looks good here.
>
>Out of curiosity, was this hiding before, or did it only come about due
>to our recent moves to the work-shared kernel builds ?
I'm being dense I guess. I went to go verify what virtual/kernel
do_populate_sysroot is doing in the current state of things, in order to
be sure it copied over the right files, and I couldn't find it quickly.
Where is this defined?
--
Darren Hart
Intel Open Source Technology Center
next prev parent reply other threads:[~2015-01-27 15:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-27 15:29 [PATCH] image: Add missing depends on virtual/kernel for depmod data Richard Purdie
2015-01-27 15:45 ` Bruce Ashfield
2015-01-27 15:48 ` Hart, Darren [this message]
2015-01-27 16:18 ` Richard Purdie
2015-01-27 16:47 ` Hart, Darren
2015-01-27 16:17 ` Richard Purdie
2015-01-27 17:20 ` Dan McGregor
2015-01-27 17:36 ` Paul Eggleton
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=D0ECF2E2.B9709%darren.hart@intel.com \
--to=darren.hart@intel.com \
--cc=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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