Openembedded Core Discussions
 help / color / mirror / Atom feed
From: nitin.a.kamble@intel.com
To: richard.purdie@linuxfoundation.org, saul.wold@intel.com,
	ross.burton@intel.com, dvhart@linux.intel.com,
	bruce.ashfield@windriver.com,
	Openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] A bugfix to enable external module building on target
Date: Tue, 30 Sep 2014 13:57:27 -0700	[thread overview]
Message-ID: <cover.1412108536.git.nitin.a.kamble@intel.com> (raw)

From: Nitin A Kamble <nitin.a.kamble@intel.com>

The path /lib/modules/<kernel-version>/build was missing on the target.
It is required to build external modules on the target. The kernel-dev
package provides all the needed support files for building the external
kernel modules. This commit creates the required missing link on the
target, which enables the external modules building.

This has been tested with a simple external module on the qemux86-64 machine
with the core-image-sato-sdk image.

See this bug for more details:
  https://bugzilla.yoctoproject.org/show_bug.cgi?id=2968

Thanks,
Nitin


The following changes since commit c34775f8864f9bf9a2b32af1e3a803f7d84e11ba:

  deb_packaging: Added support for multilib (2014-09-30 14:33:31 +0100)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib nitin/misc
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=nitin/misc

Nitin A Kamble (1):
  kernel.bbclass: enable a link for external module building

 meta/classes/kernel.bbclass | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

-- 
1.8.1.4



             reply	other threads:[~2014-09-30 21:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-30 20:57 nitin.a.kamble [this message]
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

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=cover.1412108536.git.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