Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Liu Jian <jian.liu@windriver.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] kernel-devsrc: missing tools for building modules
Date: Thu, 2 Jul 2015 14:31:13 +0800	[thread overview]
Message-ID: <5594DAB1.8030406@windriver.com> (raw)
In-Reply-To: <CADkTA4NwLTbU3O=NVc2cU13OctN_k0RD_cb8t9vtMrY0V4pS6Q@mail.gmail.com>

Hi Bruce,

I test it with arm. The arch of compiled tools is still x86.
Thanks very much for your notification.

Regards!
Jian


于 2015年07月01日 22:48, Bruce Ashfield 写道:
> On Wed, Jul 1, 2015 at 2:16 AM, Jian Liu <jian.liu@windriver.com> wrote:
>> Some tools under scripts are missed and this can cause error
>> during building modules on the target
>> Build these tools by "make script".
> We have a bugzilla for this, but the change was pending some other
> re-organizations
> of the kernel source packaging.
>
> The problem with packing this is that we used to get QA errors since
> the tools don't
> match the target arch.
>
> Can you confirm that you've built, packaged and installed this on a
> non-x86 architecture ?
>
> Bruce
>
>> Also handle the .debug directories.
>>
>> Signed-off-by: Jian Liu <jian.liu@windriver.com>
>> ---
>>   meta/recipes-kernel/linux/kernel-devsrc.bb | 6 +++++-
>>   1 file changed, 5 insertions(+), 1 deletion(-)
>>
>> diff --git a/meta/recipes-kernel/linux/kernel-devsrc.bb b/meta/recipes-kernel/linux/kernel-devsrc.bb
>> index dd65788..ff03d4e 100644
>> --- a/meta/recipes-kernel/linux/kernel-devsrc.bb
>> +++ b/meta/recipes-kernel/linux/kernel-devsrc.bb
>> @@ -57,6 +57,9 @@ do_install() {
>>           # architecture (since scripts and helpers are native format).
>>           KBUILD_OUTPUT="$kerneldir"
>>           oe_runmake -C $kerneldir CC="${KERNEL_CC}" LD="${KERNEL_LD}" clean _mrproper_scripts
>> +        # Tools under scripts/ is necessary.
>> +        cross_tool_prefix=${@d.getVar('TARGET_RAW_PREFIX', True) or ""}
>> +        make -C $kerneldir CROSS_COMPILE=$cross_tool_prefix scripts
>>
>>           # As of Linux kernel version 3.0.1, the clean target removes
>>           # arch/powerpc/lib/crtsavres.o which is present in
>> @@ -71,6 +74,7 @@ do_install() {
>>   # Ensure we don't race against "make scripts" during cpio
>>   do_install[lockfiles] = "${TMPDIR}/kernel-scripts.lock"
>>
>> -PACKAGES = "kernel-devsrc"
>> +PACKAGES = "kernel-devsrc-dbg kernel-devsrc"
>> +FILES_${PN}-dbg = "${KERNEL_SRC_PATH}/scripts/.debug ${KERNEL_SRC_PATH}/scripts/*/.debug"
>>   FILES_${PN} = "${KERNEL_SRC_PATH}"
>>   RDEPENDS_${PN} = "bc"
>> --
>> 1.8.5.2.233.g932f7e4
>>
>> --
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>

-- 
Jian Liu
Email: jian.liu@windriver.com
Office Phone: 86-10-84778539



      reply	other threads:[~2015-07-02  6:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-01  6:16 [PATCH] kernel-devsrc: missing tools for building modules Jian Liu
2015-07-01 14:48 ` Bruce Ashfield
2015-07-02  6:31   ` Liu Jian [this message]

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=5594DAB1.8030406@windriver.com \
    --to=jian.liu@windriver.com \
    --cc=bruce.ashfield@gmail.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