Signed-off-by: Khem Raj <raj.khem@...> --- recipes/gcc/gcc-4.5.inc | 13 +- recipes/gcc/gcc-4.5/arm-bswapsi2.patch | 13 -

This looks to be against meta-oe instead of oe-core, but I guess you're testing patchwork? 2011/2/17 Khem Raj <raj.khem@...>

This is a dummy patch, Yes I am testing the mailing list and patchwork correct :)

Signed-off-by: Khem Raj <raj.khem@...> --- recipes/gcc/gcc-4.5.inc | 13 +- recipes/gcc/gcc-4.5/arm-bswapsi2.patch | 13 -

Signed-off-by: Khem Raj <raj.khem@...> --- recipes/gcc/gcc-4.5.inc | 13 +- recipes/gcc/gcc-4.5/arm-bswapsi2.patch | 13 -

Hi, What's the status on the oe-core repo? regards, Koen

I have it setup. I have also a local copy of yocto ready to be pushed to populate it. I have only removed bitbake from it thus far. I did not push it since I thought to do it after todays meeting and

Thanks for the update! I'm asking this because I want to get http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/setup-scripts/log/?h=oe-core into shape so I can have people use that to setup all

Thanks to Richards hint of setting BBFETCH2 in shell env the script can now build console-image using bitbake master. So angstrom is in a good shape when OE-core goes live :) regards, Koen

Hello all openembedded-core is live now. You can clone it by git clone git://git.openembedded.org/openembedded-core any patches that are sent to openembedded-core mailing list are captured by

Thanks! If you checkout the oe-core branch of the angstrom setup-scripts[1] you can build console-image for the yocto machines and some TI machines (beagleboard, hawkboard, pandaboard, etc). For

thanks Koen for pointing out the cgit thing. So now its available on cgit as well for web viewing. http://git.openembedded.org/cgit.cgi/openembedded-core/ I will try that

As per TSC decision OE-core will only have qemu machines. This leaves the conf/machine/include file intact Signed-off-by: Koen Kooi <koen@...> --- meta/conf/machine/atom-pc.conf

Hi, Due to a misconfiguration in my proxy setup bitbake failed to fetch some things. It took me a while to figure out that the proxy setup was broken, because the error bitbake gave me

* Add support for using SOC_FAMILY in the COMPATIBLE_MACHINES setting for a recipe. * This will allow recipes to work for entire families of devices without having to maintain/update the

I suspect: http://git.pokylinux.org/cgit.cgi/poky/commit/?id=91c0b3a2e6d006224d8d2b661ca7528e9d036f1b which would at least make the error clearer... Yes, I know I need to get that back to bitbake

That should be fixed now. regards, Koen

Hi, Is anyone already working on merging in the latest yocto changes? I can take a stab at creating a patchset if noone is has already done that. regards, Koen

Since Khem is at SCALE and I'm watching over the release, I say go for it. -- Tom Rini Mentor Graphics Corporation

This merges in the yocto changes that were made since we split off oe-core, minus changes made to bitbake since oe-core doesn't ship that anymore. Pull URL: