All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: poky@o-hand.com
Cc: Richard Purdie <richard@openedhand.com>
Subject: Re: Building kernel modules outside of kernel recipe
Date: Fri, 12 Nov 2010 06:04:56 -0700	[thread overview]
Message-ID: <4CDD3B78.7040208@mlbassoc.com> (raw)
In-Reply-To: <1286376546.15840.5993.camel@rex>

On 10/06/2010 08:49 AM, Richard Purdie wrote:
> On Wed, 2010-10-06 at 08:20 -0600, Gary Thomas wrote:
>> I filed a bug on this last month:
>>     http://bugzilla.pokylinux.org/show_bug.cgi?id=241
>>
>> Richard, you made a comment about how the emenlow machine works around
>> this, but I'm not seeing how this is done in the recipes/conf files.
>>
>> Any hints?  Maybe I can see how to extend this for all targets.
>
> http://git.pokylinux.org/cgit/cgit.cgi/poky/tree/meta-emenlow/packages/psb-kernel-source/psb-kernel-source-4.42.0/build.patch
>
> See the change to psb-kernel-source-4.42.0/Makefile

Sorry, but these changes will only work when the target architecture
is execute-compatible with the host machine.  These are host executables
that need to be [re]built and the lines inserted into the Makefile will
end up building target executables.  For the PSB kernel, it works fine
since it's x86 and your build host will be x86 or ia64.  It falls apart
for me since my target is ARM.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


           reply	other threads:[~2010-11-12 13:05 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1286376546.15840.5993.camel@rex>]

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=4CDD3B78.7040208@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=poky@o-hand.com \
    --cc=richard@openedhand.com \
    /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.