[yocto] Build external module against Yocto kernel

[Bruce Ashfield]

On 13-01-24 02:58 PM, John Mehaffey wrote:
> On Wed, Jan 23, 2013 at 7:17 AM, Patrick Turley
> <PatrickTurley at gamestop.com <mailto:PatrickTurley at gamestop.com>> wrote:
>
>
>     On Jan 23, 2013, at 7:48 AM, Bruce Ashfield
>     <bruce.ashfield at windriver.com <mailto:bruce.ashfield at windriver.com>>
>       wrote:
>      > On 13-01-23 12:34 AM, Patrick Turley wrote:
>      >>
>      >> On Jan 22, 2013, at 11:17 PM, Bruce Ashfield
>     <bruce.ashfield at windriver.com <mailto:bruce.ashfield at windriver.com>>
>     wrote:
>      >>
>      >>> On 13-01-23 12:14 AM, Patrick Turley wrote:
>      >>>> On Jan 22, 2013, at 10:43 PM, Bruce
>     Ashfield<bruce.ashfield at windriver.com
>     <mailto:bruce.ashfield at windriver.com>>  wrote:
>      >>>>> On 13-01-22 9:26 PM, Patrick Turley wrote:
>      >
>      > Argh. I'll have to just run the commands myself and stop spamming the
>      > list with ideas :) It's just a matter of making lkc accept the
>     defaults
>      > (i.e. you could also use allyesconfig, or allnoconfig) or even better
>      > not trigger that config check at all.
>
>     You're very kind to have spent so much time on my problem already. I
>     look forward to hearing back.
>
>
> It sounds like you are building for a board with an ARCH other than i386
> (the default).
>

Ah yes .. it can definitely be this. I always have an ARCH on the
command line when I invoke the oldconfig.

In theory we shouldn't need the oldconfig at all either, just the arch
on the build line with making the scripts.

Cheers,

Bruce

> You need to either run it in a devshell or use "make ARCH=<arch> oldconfig".
>
> -mehaf
>
>
>     _______________________________________________
>     yocto mailing list
>     yocto at yoctoproject.org <mailto:yocto at yoctoproject.org>
>     https://lists.yoctoproject.org/listinfo/yocto
>
>