From: Darren Hart <dvhart@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Patch for fixing build issues with external kernel modules.
Date: Mon, 09 May 2011 09:28:06 -0700 [thread overview]
Message-ID: <1304958486.18625.11.camel@doubt> (raw)
In-Reply-To: <201105090016.46391.leitl@fim.uni-passau.de>
On Mon, 2011-05-09 at 00:16 +0200, Franz Leitl wrote:
> Hi,
>
> I've tried to get compcache kernel module building against 2.6.34 from shr-
> core but found some issues with kernel.bbclass and module.bbclass.
>
> The kernel.bbclass deletes the .c files from scripts directory which are later
> needed by make prepare to recreate bound.h and other files. Compcache kernel
> module, for example, depends on bounds.h.
The bounds.h should not need to be recreated. It is created during the
build of the kernel, and since 2.6.26, the makefile knows not to remove
it.
> The module.bbclass finally needs to call "make prepare" and also set
> KERNEL_PATH in do_install when calling oe_runmake to get everything
> installed correctly.
Since we copy over the source tree after a simple clean, make prepare
should also not be necessary:
clean - Remove most generated files but keep the config and
enough build support to build external modules
So I'm curious about your workflow and why you are hitting these two
issues. Can you share your recipes?
> I also added KERNELDIR as compcache's Makefile is using it and the
> classes from classic OE had it also set.
I'm not familiar with compcache, but generally speaking we can't get in
the habit of modifying the recipe classes to support whatever variables
random external module Makefile expect. See recipes-kernel/hello-mod for
an example Makefile that builds an external module using the existing
infrastructure. You may just need a patch to the compcache Makefile for
it to work within the existing infrastructure.
>
> Can someone please review the attached patch?
>
>
> Regards,
> Franz
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2011-05-09 16:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-08 22:16 Patch for fixing build issues with external kernel modules Franz Leitl
2011-05-08 22:30 ` Franz Leitl
2011-05-09 16:28 ` Darren Hart [this message]
2011-05-09 17:32 ` Franz Leitl
2011-05-09 17:53 ` Koen Kooi
2011-05-09 18:23 ` Darren Hart
2011-05-09 18:38 ` Franz Leitl
2011-05-09 20:53 ` Darren Hart
2011-05-10 1:40 ` Franz Leitl
2011-05-10 1:56 ` Franz Leitl
2011-05-10 20:23 ` Darren Hart
2011-05-10 22:50 ` Franz Leitl
2011-05-23 23:37 ` Darren Hart
2011-05-24 0:19 ` Darren Hart
2011-05-09 18:20 ` 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=1304958486.18625.11.camel@doubt \
--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