Folks, Apologies for the extended absence of bugzilla.yoctoproject.org, it is back up now and working. As we head into the next phase of Poky / Yocto Metadata 1.0, we need to have people evaluate

Thanks for the catch-up. I do remember that you dig it out but not realize related here. :-) Thanks Kevin

This needs to be "rm -rf", there is another patch in master that takes care of this: 21fafc889e81411735de7d04ffe504e5cff4830d -- Darren -- Darren Hart Intel Open Source Technology Center Yocto

Many of these items are resolved in the mhatle/rpm5 branch that is part of poky-contrib. I'm trying to get the work finished for inclusion in the next day or so. But for a minimal image, RPM likely

What's the kernel version on the working build ? Do you have the dmesg output from the working/non working boots handy ? Also the .config from your non-working boot would also be handy. This smells

I've built poky-image-minimal for a machine that's based on qemux86.conf. I've create a modified copy to target x86 hardware and made sure usbhost and usbgadget are in the MACHINE_FEATURES. If I

Chris Tapp wrote: Hi there, The rpm packaging version does has some issues (half-statically built binaries, full SAT-solver which might be an overkill for a minimal image, etc). I got much better

Hi Darren, I'm just trying to estimate the minimal footprint that can be achieved for an image with a basic set of features in order to have a comparison. In march I'll participate in a local

Chris, Take a look at your local.conf and see what is included on EXTRA_IMAGE_FEATURES. Removing them you will save lots of space too. Regards, -- *dS Diego Sueiro /*long live rock 'n roll*/

Folks, especially regular contributors: Are they are any volunteers willing to setup a Debian 6 machine and build Poky / Yocto to determine if we have any problems. Since we will release 1.0 right

Hi, recently (from this week), I continuously meet build error (x86 and arm). Seems it's a kind of lock problem, eg: complaining that No such file or directory:

This is a known issue in 0.9. the switch from ipk to rpm leaves some temporary files in the final ext3 rootfs, which results the large size. This configuration option only works when it exceeds the

What size of an image are you hoping to achieve? -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel

Hi all, This is the sanity test report for Laverne build(20110121). Since bugzilla is not accessible, for these new bugs, we give a simple summary in this report and will report them on

I know this is probably a basic question, but I'm not having much luck ! I've built poky-image-minimal for atom-pc using the 0.9 Poky release. This gives me an ext3 rootfs of over 80MB, which

Right, we do have old uclibc recipes in Poky still I believe although they would need updating after the recent toolchain bootstrap changes. I do know people using uclibc actively in OE and this may

I think these are due to the fact Koen is using rm_work (confirmed by Koen over irc). I agree we need to work out a way to handle this, it should help anyone trying to find a fix though. It should be

And another one: NOTE: package pango-1.28.3-r1.0: task do_package: Started ERROR: Error executing a python function in

So far uclibc has not been a goal of the Yocto project. With the minimum size of flash parts these days, the configurability of eglibc and the mklibs library optimizer... the use-case for uclibc is

Switchting from usrp-e1xx (armv7a) to beagleboard (also armv7a) and building console-image again: NOTE: package perl-5.12.2-r0: task do_package: Started ERROR: Function 'perl_package_preprocess'