From: Darren Hart <dvhart@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Koen Kooi <koen@dominion.thruhere.net>
Subject: Re: [PATCH] kernel.bbclass: fix external module building
Date: Fri, 20 Jul 2012 00:20:01 -0700 [thread overview]
Message-ID: <500906A1.8000600@linux.intel.com> (raw)
In-Reply-To: <1342762570-29343-1-git-send-email-raj.khem@gmail.com>
On 07/19/2012 10:36 PM, Khem Raj wrote:
> From: Denis Carikli <GNUtoo@no-log.org>
>
> Without that fix we have the following while compiling compat-wireless.
> include/linux/mmzone.h:18:30: fatal error: generated/bounds.h: No such file or directory
>
> Note that the compat-wireless recipe will be added in another commit.
>
> Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>
> Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
> ---
> meta/classes/kernel.bbclass | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
> index 08b5e61..ce4d7de 100644
> --- a/meta/classes/kernel.bbclass
> +++ b/meta/classes/kernel.bbclass
> @@ -187,6 +187,9 @@ kernel_do_install() {
> cp arch/powerpc/lib/crtsavres.o $kerneldir/arch/powerpc/lib/crtsavres.o
> fi
>
> + # Necessary for building modules like compat-wireless.
> + cp include/generated/bounds.h $kerneldir/include/generated/bounds.h
> +
Hrm... I'm not clear on why this is necessary. I understand why you need
bounds.h... but I don't see why it isn't there already.
A few lines up we do:
cp -fR * $kerneldir
Which should cover include/generated/bounds.h...
Perhaps "make -C $kerneldir _mrproper_scripts" clears that out... Ah,
yes, that seems to be the case. Grumble.
OK,
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2012-07-20 7:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-20 5:36 [PATCH] kernel.bbclass: fix external module building Khem Raj
2012-07-20 7:20 ` Darren Hart [this message]
2012-07-20 10:07 ` Paul Eggleton
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=500906A1.8000600@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=koen@dominion.thruhere.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.