Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: kernel: building target-arch scripts/* to include in kernel-headers package
Date: Mon, 25 Jun 2012 16:33:22 -0700	[thread overview]
Message-ID: <4FE8F542.2070304@linux.intel.com> (raw)

I'm working on a patch series to provide a kernel-headers package which
allows for the compilation of Linux kernel modules on the target. I
currently have something working, but it requires that I first build the
scripts/* binaries on the target, prior to trying to build a module.

	# cd /usr/src/kernel-headers
	# make scripts

Then I can build modules:

	# cd /home/root/hello-mod/files
	# export KERNEL_SRC=/usr/src/kernel-headers
	# make

And test:

	# insmod hello.ko
	# rmmod hello.ko
	# dmesg | tail -n2
	Hello World!
	Goodbye Cruel World!

I would like to package the target-arch scripts binaries with the
kernel-headers package, but I'm not sure how to go about building both
the native and the target binaries as part of the kernel building
process. Does it make sense to build these as part of the do_install()
task after I've moved the files from the linux recipe's workdir and
removed the host-arch binaries from scripts?

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel




             reply	other threads:[~2012-06-25 23:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-25 23:33 Darren Hart [this message]
2012-06-26  5:19 ` kernel: building target-arch scripts/* to include in kernel-headers package Khem Raj
2012-06-26  5:53   ` Khem Raj
2012-06-26 16:15     ` Darren Hart
2012-06-26 15:58   ` Darren Hart
2012-06-26 16:27     ` Koen Kooi
2012-06-26 17:12       ` Darren Hart

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=4FE8F542.2070304@linux.intel.com \
    --to=dvhart@linux.intel.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