All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anders Darander <anders@chargestorm.se>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-oe][PATCH 0/1] Fix external module compilations
Date: Tue, 5 Jul 2011 14:48:10 +0200	[thread overview]
Message-ID: <201107051448.10772.anders@chargestorm.se> (raw)
In-Reply-To: <1309869522.2410.0.camel@phil-desktop>


* Phil Blundell Phil Blundell <philb@gnu.org> [07/05/11 02:38 PM]:
> 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?

Yes, it is certainly a sad state.

The primary difference seems to be some changes in the uImage-related code, and 
that meta-oe has some initramfs-support in its kernel.bbclass.

Can someone with deeper knowledge comment on this? I guess that it shouldn't 
be any real problems in getting the initramfs support code merged into oe-
core. 

What about the differences in the uImage code? (I haven't really looked into 
the differences).

Cheers,
Anders



      reply	other threads:[~2011-07-05 12:51 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 ` [meta-oe][PATCH " Phil Blundell
2011-07-05 12:48   ` Anders Darander [this message]

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=201107051448.10772.anders@chargestorm.se \
    --to=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.