From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Parker Mackenzie <wparkermackenzie@live.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Cross Compile Kernel Modules
Date: Sat, 5 Oct 2013 00:45:05 -0400 [thread overview]
Message-ID: <524F9951.5010806@windriver.com> (raw)
In-Reply-To: <BLU169-W12FA95B48C2052097CC9A1B2100@phx.gbl>
On 13-10-04 5:06 PM, Parker Mackenzie wrote:
> Bruce, No problem... you got me on the right path.
>
> Bitbake now completes successfully after adding python-core and bash to IMAGE_INSTALL_append.
>
>
>
> Looking again at the presentation it indicated I also needed to do the following:
> make oldconfig ARCH=arm
> - This completed successfully
>
> make scripts ARCH=arm
> - This fails with the following errors:
>
> [parker@jasper kernel]$ make scripts ARCH=arm
> scripts/kconfig/conf --silentoldconfig Kconfig
> CC scripts/mod/empty.o
> gcc: error: unrecognized command line option ‘-mlittle-endian’
> gcc: error: unrecognized command line option ‘-mapcs’
> gcc: error: unrecognized command line option ‘-mno-sched-prolog’
> gcc: error: unrecognized argument in option ‘-mabi=aapcs-linux’
> gcc: note: valid arguments to ‘-mabi=’ are: ms sysv
> gcc: error: unrecognized command line option ‘-mno-thumb-interwork’
> make[2]: *** [scripts/mod/empty.o] Error 1
> make[1]: *** [scripts/mod] Error 2
> make: *** [scripts] Error 2
>
> The cross compiler seems to be correct...:
> [parker@jasper kernel]$ echo $CC
> arm-poky-linux-gnueabi-gcc -march=armv7-a -mthumb-interwork -mfloat-abi=softfp -mfpu=neon --sysroot=/home/parker/Projects/beagleboard/yocto/poky-dylan-9.0.2/sdk/sysroots/armv7a-vfp-neon-poky-linux-gnueabi
>
But for the scripts, you won't be using the cross compiler, they are
native to your arch.
Check your environment, are CC and CFLAGS set ? How exactly are you
invoking that command (i.e. from where, just a shell in the kernel
source directory?). If non native flags and compiler is leaking into
the build, you'll get exactly the error that you are seeing.
From the error, looks like the native gcc was used, and it was fed
the ARM flags. Not what it'll like :)
Cheers,
Bruce
>
> Trying to build this on:
> Linux jasper 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
>
>
>
>
>
>
>>
>> Right! I typed in "python" from memory :) In fact, what I typically have is
>> a full set of python dependencies, including python-dev, which picks
>> up what I need.
>>
>> Cheers,
>>
>> Bruce
>>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
prev parent reply other threads:[~2013-10-05 4:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-03 20:08 Cross Compile Kernel Modules Parker Mackenzie
2013-10-03 20:29 ` Bruce Ashfield
2013-10-04 0:21 ` Parker Mackenzie
2013-10-04 0:53 ` Bruce Ashfield
2013-10-04 11:05 ` Hans Beckérus
2013-10-04 11:22 ` Parker Mackenzie
2013-10-04 12:41 ` Bruce Ashfield
2013-10-04 21:06 ` Parker Mackenzie
2013-10-05 4:45 ` Bruce Ashfield [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=524F9951.5010806@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=wparkermackenzie@live.com \
--cc=yocto@yoctoproject.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.