From: "Kamble, Nitin A" <nitin.a.kamble@intel.com>
To: "Ashfield, Bruce (Wind River)" <bruce.ashfield@windriver.com>,
"richard.purdie@linuxfoundation.org"
<richard.purdie@linuxfoundation.org>,
"Wold, Saul" <saul.wold@intel.com>,
"Burton, Ross" <ross.burton@intel.com>,
"dvhart@linux.intel.com" <dvhart@linux.intel.com>,
"Openembedded-core@lists.openembedded.org"
<Openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] kernel.bbclass: enable a link for external module building
Date: Tue, 30 Sep 2014 21:14:47 +0000 [thread overview]
Message-ID: <D0506A39.6455%nitin.a.kamble@intel.com> (raw)
In-Reply-To: <542B19F8.4030805@windriver.com>
On 9/30/14, 2:00 PM, "Bruce Ashfield" <bruce.ashfield@windriver.com> wrote:
>On 2014-09-30, 4:57 PM, nitin.a.kamble@intel.com wrote:
>> From: Nitin A Kamble <nitin.a.kamble@intel.com>
>>
>> To build external modules, the link /lib/modules/<kernel-version>/build
>> must exist, and point to the proper kernel source area.
>>
>> The kernel-dev package already provides the needed source files. Now
>> putting a link in place to unblock the external module building.
>
>This description is not entirely accurate, at least from my point of
>view.
>
>You can build external modules on the target without this link .. it is
>that many scripts and utilities look in this location for the kernel
>source.
>
>We are fixing that case, not the general case of building an external
>module.
I see. Thanks for pointing it out. I guess, the bug entry missed this
information. I will fix the commit log and resend it.
Nitin
>
>Cheers,
>
>Bruce
>
>>
>> Fixes Bug:
>> [YOCTO #2968]
>>
>> Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
>> ---
>> meta/classes/kernel.bbclass | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
>> index 78b33ce..5ac4ff4 100644
>> --- a/meta/classes/kernel.bbclass
>> +++ b/meta/classes/kernel.bbclass
>> @@ -213,6 +213,7 @@ kernel_do_install() {
>> #
>> kerneldir=${D}${KERNEL_SRC_PATH}
>> install -d $kerneldir
>> + ln -sf ${KERNEL_SRC_PATH} "${D}/lib/modules/${KERNEL_VERSION}/build"
>>
>> #
>> # Store the kernel version in sysroots for module-base.bbclass
>> @@ -346,7 +347,7 @@ PACKAGES = "kernel kernel-base kernel-vmlinux
>>kernel-image kernel-dev kernel-mod
>> FILES_${PN} = ""
>> FILES_kernel-base = "/lib/modules/${KERNEL_VERSION}/modules.order
>>/lib/modules/${KERNEL_VERSION}/modules.builtin"
>> FILES_kernel-image = "/boot/${KERNEL_IMAGETYPE}*"
>> -FILES_kernel-dev = "/boot/System.map* /boot/Module.symvers*
>>/boot/config* ${KERNEL_SRC_PATH}"
>> +FILES_kernel-dev = "/boot/System.map* /boot/Module.symvers*
>>/boot/config* ${KERNEL_SRC_PATH} /lib/modules/${KERNEL_VERSION}/build"
>> FILES_kernel-vmlinux = "/boot/vmlinux*"
>> FILES_kernel-modules = ""
>> RDEPENDS_kernel = "kernel-base"
>>
>
prev parent reply other threads:[~2014-09-30 21:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 20:57 [PATCH 0/1] A bugfix to enable external module building on target nitin.a.kamble
2014-09-30 20:57 ` [PATCH 1/1] kernel.bbclass: enable a link for external module building nitin.a.kamble
2014-09-30 21:00 ` Bruce Ashfield
2014-09-30 21:14 ` Bruce Ashfield
2014-09-30 21:14 ` Kamble, Nitin A [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=D0506A39.6455%nitin.a.kamble@intel.com \
--to=nitin.a.kamble@intel.com \
--cc=Openembedded-core@lists.openembedded.org \
--cc=bruce.ashfield@windriver.com \
--cc=dvhart@linux.intel.com \
--cc=richard.purdie@linuxfoundation.org \
--cc=ross.burton@intel.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