From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] kernel: restore scripts in the sysroot
Date: Mon, 7 Oct 2013 12:20:46 -0400 [thread overview]
Message-ID: <5252DF5E.6010902@windriver.com> (raw)
In-Reply-To: <1381162713.29912.16.camel@ted>
On 13-10-07 12:18 PM, Richard Purdie wrote:
> On Mon, 2013-10-07 at 11:20 -0400, Bruce Ashfield wrote:
>> I had it slightly wrong. Try:
>>>
>>> kernelheaders_sstate_postinst () {
>>> if [ "${BB_CURRENTTASK}" = "populate_sysroot" -o "${BB_CURRENTTASK}" = "populate_sysroot_setscene" ]
>>> then
>>> ( cd ${KERNEL_SRC_PATH};
>>> oe_runmake scripts
>>> )
>>> fi
>>> }
>>>
>>> since the files are actually installed at this point, therefore we
>>> operate on the final location.
>>
>> That's the kicker, I can't get the right variable to find the final
>> location, KERNEL_SRC_PATH is set to /usr/src/kernel, so we can't operate
>> on it directly. When things were runing in the sysroot_append, the
>> kernel src was staged, and then operated on, then it makes it into the
>> sysroot. Here, we could operate on the STAGING_KERNEL, which is in the
>> sysroot, but stripped of the scripts. Perhaps that is the answer, but
>> I need to confirm that scripts installed in that location would be
>> available to the out of tree module builds that are looking for modpost
>> and friends.
>
> Guessing again (third time lucky?),
>
> cd ${STAGING_DIR_KERNEL};
Yah, that's where it lives. I'm building now and trying to validate Khem's
use case.
Bruce
>
> ?
>
> Cheers,
>
> Richard
>
>
next prev parent reply other threads:[~2013-10-07 16:20 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-04 0:02 [PATCH 0/1] kernel: provide scripts in the sysroot Bruce Ashfield
2013-10-04 0:02 ` [PATCH 1/1] kernel: restore " Bruce Ashfield
2013-10-04 0:58 ` Khem Raj
2013-10-04 0:59 ` Bruce Ashfield
2013-10-04 7:46 ` Richard Purdie
2013-10-04 12:42 ` Bruce Ashfield
2013-10-04 20:23 ` Khem Raj
2013-10-07 5:02 ` Bruce Ashfield
2013-10-07 9:58 ` Richard Purdie
2013-10-07 15:20 ` Bruce Ashfield
2013-10-07 16:18 ` Richard Purdie
2013-10-07 16:20 ` Bruce Ashfield [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-10-08 21:12 [PATCH 0/1] " Bruce Ashfield
2013-10-08 21:12 ` [PATCH 1/1] " Bruce Ashfield
2013-11-19 17:37 ` Mike Crowe
2013-11-19 17:46 ` Phil Blundell
2013-11-19 17:54 ` Bruce Ashfield
2013-11-19 18:17 ` Bruce Ashfield
2013-11-19 22:29 ` Khem Raj
2013-11-19 22:36 ` Richard Purdie
2013-11-19 22:39 ` Khem Raj
2013-11-19 22:45 ` Richard Purdie
2013-11-20 2:59 ` Khem Raj
2013-11-20 4:43 ` Bruce Ashfield
2013-11-19 22:37 ` Bruce Ashfield
2013-11-19 22:42 ` Richard Purdie
2013-11-19 22:46 ` Bruce Ashfield
2013-11-19 23:44 ` Phil Blundell
2013-11-19 22:48 ` Bruce Ashfield
2013-11-19 23:41 ` Phil Blundell
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=5252DF5E.6010902@windriver.com \
--to=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