Richard/Saul, Here are the updated SRCREVs for Darren's recent atom-pc-rt work and Tom's systemtap configs. Cheers, Bruce Pull URL: git://git.pokylinux.org/poky-contrib.git Branch: zedd/kernel

Yes. Poky.git is a repo which contains a bunch of branches. One simple way you can verify is to use "git branch", and if "*master" is shown then you're using the master branch. If it still doesn't

What's the patch you made for autobuilder? I think the patch I sent out yesterday can prevent the cascading failure but it has not been checked in yet. Best Regards, Jiajun

Are your package lists identical ? Sounds like host contamination to me and perf is deciding to build perl or not perl based on what the host has installed. This works .. or to get the functionality

Hi, I have two build machines: x86 ubuntu 10.04 at work x86_64 ubuntu 10.04 at home At home all things goes ok. But at work perf has failed. The problem is LIBPERL. I can't understand why but at

Hi Richard, As I mentioned in IRC, we've noticed that bitbake behaves differently on 64bit and 32bit machines from SDKMACHINE setup perspective. It never enforces SDKMACHINE to be set in local.conf

Yeah, it's strange that this starts happening seemingly out of the blue - nothing wrt this has changed recently AFAICS. Coincidentally, I was going to look at perf scripting next week - guess I'll

I saw this one as well, but hadn't gone back to look at it yet. Did something change underneath us? I haven't updated any parts of the recipes or kernel that would have triggered the new failure. Or

All, The current nightly based on d82f205cfa790b40e132e11b7937050bc3b97ff3 is showing 3 build failures so far. Machine: qemux86 Failure: intermittent tasks_0.18 failure at do_compile Description:

Yes, it's make 3.82 related. My gut-feeling is that FC12 should have an older version which ends up wrong here. :-) OK, I remembered that there're a series of patches to make FC14 happy after

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