From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] kernel: restore scripts in the sysroot
Date: Thu, 3 Oct 2013 20:59:47 -0400 [thread overview]
Message-ID: <524E1303.3010302@windriver.com> (raw)
In-Reply-To: <24D616E6-3C79-4C7A-AFED-BE63DAE239BF@gmail.com>
On 13-10-03 8:58 PM, Khem Raj wrote:
>
> On Oct 3, 2013, at 5:02 PM, Bruce Ashfield <bruce.ashfield@windriver.com> wrote:
>
>> When building against the sysroot, out of tree modules can require modpost
>> and other utilities normally found in the kernel's scripts directory. For
>> the kernel source in the staging dir, these scripts have been removed to
>> avoid mixing archiectures when packaging kernel-dev (among other things).
>>
>> Rather than further complicate the kernel's install rule, or its packaging,
>> we can jump into the sysroot and restore the scripts by building them, hence
>> making them available to packages that need them.
>>
>> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
>> ---
>> meta/classes/kernel.bbclass | 8 ++++++++
>> 1 file changed, 8 insertions(+)
>>
>> diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
>> index 4acfb7e..d856e31 100644
>> --- a/meta/classes/kernel.bbclass
>> +++ b/meta/classes/kernel.bbclass
>> @@ -294,6 +294,14 @@ do_install[prefuncs] += "package_get_auto_pr"
>>
>> sysroot_stage_all_append() {
>> sysroot_stage_dir ${D}${KERNEL_SRC_PATH} ${SYSROOT_DESTDIR}${KERNEL_SRC_PATH}
>> +
>> + # Restore kernel scripts in the sysroot, since they had to be removed during
>> + # packaging to avoid mismatched arch QA errors, but are required/useful when
>> + # packages like out of tree kernel modules are built. Rather than playing QA
>> + # games, it is easier to just do this work in the sysroot.
>> + ( cd ${SYSROOT_DESTDIR}${KERNEL_SRC_PATH};
>
> This was cd ${SYSROOT_DESTDIR}${KERNEL_SRC_PATH}/scripts in my patch but I will test out this one too.
> but this is ok since
Thanks. I went with habit and did it right from the top level. I see
modpost in my sysroot, but I definitely want to get your confirmation
that it works for you as well.
Bruce
>
> ifeq ($(KBUILD_EXTMOD),)
> # Additional helpers built in scripts/
> # Carefully list dependencies so we do not try to build scripts twice
> # in parallel
> PHONY += scripts
> scripts: scripts_basic include/config/auto.conf include/config/tristate.conf \
> asm-generic
> $(Q)$(MAKE) $(build)=$(@)
>
>
>> + oe_runmake scripts
>> + )
>> }
>>
>> kernel_do_configure() {
>> --
>> 1.8.1.2
>>
>
next prev parent reply other threads:[~2013-10-04 0:59 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 [this message]
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
-- 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=524E1303.3010302@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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 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.