Check out http://www.yoctoproject.org/blogs/davest/2010/10/7/four-architectures-grooving-together,my latest post to the Yocto Project blog. Some photos there of the UPnP demo. I also plan to post

The rest of the config has been moved to meta-extras, and we'd need to do a bit of kernel work, but it has worked in the past, and could work again in the future. In other words 'I

2010/11/1 Stewart, David C <david.c.stewart@...>: Dave, the demo looked indeed quite impressive, and actually I was trying to fetch the sources, but .... git clone does not work for me. I've

Hi Frans, It looks like anonymous access to the git repository isn't enabled. I can clone it using ssh:// but not get the same error as you when using git:// We'll have someone resolve this later

Hello, Leading up to our 0.9 release, our autobuilder has been building an increasing number of targets for our nightly-release buildset. We've now reached the point that the nightly build takes more

There doesn't just have to be one build machine, we are going to end up needing multiple machines and we can split the load between them quite easily. I think there is going to be a second machine

I can buy another server and contribute it to the build effort. I had intended to buy one this quarter to begin hosting yoctoproject.org and a source mirror, but we could offload part of the builds to

These was a problem with anonymous clones of this repository but this should be fixed now, sorry about that. Cheers, Richard

(Sorry for the late response, today's my first day back from CELF) My preference is staying with the Poky 'arch' naming... but renaming to noarch is fine, and unless Richard or someone else sees an

How about customizing the nightly build to build part of targets for every day? For example, x86/x86_64 for Monday, atom-pc/emenlow for Tuesday..... etc. And we can schedule a new build task for

These test suites can help to find bugs from user level to kernel. It's hard to put them as components under just one product. User can decide the product and add note in bug title that the bug is for

#! /bin/sh # Hello, case $Debian_build_system in lenny_amd64) cat <<EOF [...] |

My proposal -- similar bug slightly different: Poky Build System Bitbake Documentation General Poky Distribution Runtime Distribution -- Poky embedded linux distribution Documentation

The divide between User Space and Tool Chain is a bit vague. For instance, I would generally expect to see glibc under User Space, but your description seems to place it under Tool Chain. Please keep

I think this is where the Bugzilla description needs to be verbose. Toolchain for me includes: userspace kernel headers (but not the kernel), binutils, gcc, "the libc" (uclibc, glibc, eglibc), and

We'll also want to update this document after we make these changes: https://wiki.yoctoproject.org/wiki/Bugzilla_Configuration_and_Bug_Tracking We might want to streamline that doc a bit to better

Good point. (See my reply to Mark's email) I think my lines might have run together! It was meant to be separate, and this looks like a good break down. Sau!

Add Configurations - for the config/site data Remember this is not a Distribution, I think Yocto (Poky?) Meta-Data / Recipes and then the following components Add: User Space Recipes (this could

Hi, I don't have answers to all of the failures but let me try and respond to the ones I have some ideas about: At a guess this is a 64 bit kernel and a 32 bit userspace? What does "uname -a"

This is too much separation, having over categorization of the kernel defects at this point is overkill. I'd suggest three categories: - kernel build (which often transitions to straight up