[yocto] bitbake -c populate_sdk -v poky-image

[Navani Srivastava]

>>You should set SDKMACHINE if you need the machine that runs the SDK to be
a
different architecture from the machine
Please find the local.conf file which clearly shows SDKMACHINE is i686 and
I want to build for arm1136 arch.. So MACHINE ??= "EBboard" is given where
EBboard refers to arm1136 architecture..
Not able to find any problem in configurations..

/opt/poky/1.3.2/sysroots/i686-pokysdk-linux/usr/bin/armv6-vfp-poky-linux-gnueabi/arm-poky-linux-gnueabi-gcc
test.c
test.c:3:19: fatal error: stdio.h: No such file or directory

error shows that I have problem in cross toolchain...  Have yocto ever
faced such kind of issue with populate_sdk before ?


On Thu, Aug 29, 2013 at 1:43 PM, Paul Eggleton <
paul.eggleton at linux.intel.com> wrote:

> On Thursday 29 August 2013 10:11:31 Navani Srivastava wrote:
> > In order to execute
> > "bitbake -c populate_sdk poky-image" are we supposed to declare
> > BUILD_ARCH or SDK_ARCH somewhere in local.conf file?
> > Yocto Documentation has not mentioned anything like that. Just a doubt as
> > "bitbake poky-image" is working fine though populate_sdk is giving
> problem..
>
> You should set SDKMACHINE if you need the machine that runs the SDK to be a
> different architecture from the machine that you're running the build on,
> otherwise it will just use the same one.
>
> We're aware the documentation is lacking on -c populate_sdk, and we're
> addressing that in the documentation for the next release.
>
> Cheers,
> Paul
>
> --
>
> Paul Eggleton
> Intel Open Source Technology Centre
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20130829/a4fe73c3/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: local.conf
Type: application/octet-stream
Size: 9959 bytes
Desc: not available
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20130829/a4fe73c3/attachment.obj>