From: Phil Blundell <philb@gnu.org>
To: openembedded-devel@lists.openembedded.org
Cc: Anders Darander <anders@chargestorm.se>
Subject: Re: [meta-oe][PATCH 0/1] Fix external module compilations
Date: Tue, 05 Jul 2011 13:38:41 +0100 [thread overview]
Message-ID: <1309869522.2410.0.camel@phil-desktop> (raw)
In-Reply-To: <cover.1309866872.git.anders@chargestorm.se>
On Tue, 2011-07-05 at 14:05 +0200, Anders Darander wrote:
> When compiling an external module, the compilation errors out, when
> scripts/basic/fixdep and later on scripts/mod/modpost is being requested. The
> removal of 'make -C $kerneldir _mrproper_scripts' fixes these problems.
It is a bit sad that these sorts of changes need to be done twice. Is
there a compelling reason why meta-oe needs to maintain its own version
of kernel.bbclass rather than sharing it with oe-core?
p.
next prev parent reply other threads:[~2011-07-05 12:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-05 11:55 [PATCH 0/1] Fix external module compilations Anders Darander
2011-07-05 12:05 ` [meta-oe][PATCH 1/1] kernel.bbclass: make external module compile Anders Darander
2011-07-05 12:08 ` [PATCH 0/1] Fix external module compilations Anders Darander
2011-07-05 12:38 ` Phil Blundell [this message]
2011-07-05 12:48 ` [meta-oe][PATCH " Anders Darander
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=1309869522.2410.0.camel@phil-desktop \
--to=philb@gnu.org \
--cc=anders@chargestorm.se \
--cc=openembedded-devel@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.