Everything got pulled this time In Master now Thanks Sau!

Pulled into master Thanks Sau!

Ok. I was not sure if it was specific to Fedora 14 or not. The Quick Start mentions Fedora 14 "or another distribution with GNU make 3.82" which is what I have on Fedora 12, so I thought this step

The make-native is required on Fedora14. So you don't need that step and Instead you could directly: Bitbake poky-image-sato Btw, could you post your errors? For native packages, yes the host

I am new to yocto, I have installed yacto on Fedora 12. I was trying to follow the steps in the getting started guide and was trying a build with "bitbake make-native" and got some build errors

Hi, Dave, Yes, LSB contains cron. I talked to Jiajun about choice of the profile. SDK profile simplifies QA’s test effort since it runs on both Qemu and real hardware, while LSB profile is not

I agree, it does seem odd, but since there was a standard already in place (for historical reasons, I'm sure) with emenlow and atom-pc of <machine>/<arch>/ I wanted to make sure I didn't mess up

once you've descended into machine_name, "arch" seems superfluous. Won't it be the only directory? Would it make more sense as: machines/arch/machine_name ? machines x86 qemux86 atom-pc

Hi, I have a layer and will try it. If all thinks goes well, I submit a patch. In OE I used openntpd. The busybox ntp client does not support a config file. Thanks. --

João, If you are creating a layer, then it would be best to create a busybox.bbappend file that enables the options you are looking for. You can also add an ntp client in your layer, you just need

The cross-prelink project has been updated to the latest upstream prelink SVN Revision 187 a.k.a. prelink-0.4.4. Current version of the cross-prelink is f51f4a5db605ab542ab06334fcad1d5bdba91048 The

Kevin - this is quite valuable analysis into the test failures - thank you! The one which surprises me is the cron failure. But sure enough, the Sato image I have running on my desk doesn't have

I talked a little with Dongxiao about this and it looks like he needs to improve the functionality in sstate to cope with sysroot per machine. This isn't to say that the libtool 2.4 sysroot support

Hi, all, I’d like to give a quick update about current LTP status. For detail, please check out: https://wiki.yoctoproject.org/wiki/LTP_result Generally LTP is for desktop compliance

Garman, Scott A wrote: Hi Scott, This issue may only happen with the implementation of machine specific sysroot. Currently different machines of one architecture share the same path of sysroot and

Thanks Donxiao for the info. I will make sure to test this scenario before submitting my libtool 2.4 sysroot support to ensure it is resolved. Scott -- Scott Garman Embedded Linux Distro Engineer -

The routerstation pro and mpc8315e-rdb have been validated on 2.6.37 so we can switch their preference to linux-yocto and update the machine compatibility to add them to the

Just repeating the patch header here, since it is self explanitory: The routerstation pro and mpc8315e-rdb have been validated on 2.6.37 so we can switch their preference to linux-yocto and

I recalled giving it a push before sending the pull, but I was also battling some issues with both infrastructure and poky-extras at the time. Regardless, it seems to be resolved now and shout if you

I've just looked now and I don't know if anything has changed but the head revision