Fixes [BUGID #598] The explicit addition of "bash" before "make menuconfig" is clearing variables that are required for pseudo. The end result is that menuconfig often fails silently with: ERROR:

Fixes [BUGID #598] The explicit addition of "bash" before "make menuconfig" is clearing variables that are required for pseudo. The end result is that menuconfig often fails silently with: ERROR:

Pulled into Master and Bernard Thanks Sau!

Fixes [BUGID #777] The do_install rule in u-boot.inc was installing a host tool into the target ${bindir}, which is subsequently stripped with target strip during packaging, and the obvious error

Richar/Saul, This fixes BUG 777. The u-boot package clearly uses HOST_CC and HOST_STRIP to build mkimage, so installing it into ${D}${bindir} for anything but the native mkimage is a bad idea. The

Here are the notes from the March 1st Yocto Release Tracking meeting. Thanks. - Julie Attendees: Dave, Saul, Julie, Mark, Darren, Beth, Jeff P., Jessica, Joshua, Jeff O., Tom, Richard Agenda: 1)

Hi all, This is latest Yocto bug trend chart for WW09. With developers' hard work, we have open bug number decreased a lot (from 160 to 131). And from this week, we introduce a new chart "weighted

Yeah, it looks like stale cache. http://autobuilder.yoctoproject.org/sources/git2_git.pokylinux.org.linux-yocto-2.6.37.tar.gz doesn't have local branches for

Oh, the correct information is that RC2 will be ready @ this weekend. Thanks& Regards, criping

All, This morning we had the Yocto RC1 Release Readiness Review. Notes follow. Attendees: Beth, Dave, Jessica, Paul, Joshua, Julie, Saul, Jeff O, Richard Feature Status: * We are currently

Hi, Jessica JiaJun told me that RC2 image will soon come out (Hopefully on Wednesday). So my question is that When will the repo be ready (With RC2 image). Seems we need to have some formal data for

Thanks to those that attended last week's Yocto Release Tracking Meeting! We'll have another this week. Details below. Time/Date: Tuesday, March 01, 2011, 08:00 AM US Pacific Time Dial in:

alsa is the defacto / first choice for me. That's partially why I chose to make this an optional config block for this feature. That way it is optional, and only applied to the specific qemu images

I'd wondered about this too. In general I'd suggest Yocto's position is to push for alsa drivers and see OSS as a legacy thing. As the author of chunks of ALSA SoC code, I've put that into practise

Hi Bruce, I'm a little late to the party, but was wondering what your thoughts are on the whole OSS thing. It seems we should be as consistent as possible in our various Yocto Linux kernel images. Do

The jasperforest branch just got updated, and I just submitted a SRCREV update to use that, which takes care of the perf compile error. I still see the problem with the the fetcher not getting the

Hi, As most have gathered, there are changes afoot in the OE world and we want to start increasing collaboration between Yocto and OE through the creation of an OE-Core repository which both projects

There are a couple problems with the jasperforest BSP. First, the SRCREVs need updating, which I just submitted a patch for. Even after that, though, there seems to be a problem with the kernel repo

Elizabeth Flanagan wrote on 2011-02-28: I think it'd better to run "bitbake package-index" after the "bitbake meta-toolchain-sdk", using the same configuration as meta-toolchain-sdk. It will generate

Summary ======= This weekend, we generated a release candidate for bernard based on the bernard branch of master at commit: e08dc5aaaeba61e332caab4a3df5750df6b49ac1 and for BSPs based on the bernard