From: Tom Zanussi <tom.zanussi@...> The fri2 linux-yocto-rt .bbappend is missing settings needed for use with fri2-noemgd - this adds them. Signed-off-by: Tom Zanussi

From: Tom Zanussi <tom.zanussi@...> commit 061f3187e8cbec70d5970928b6e8252cb0958f4a (meta-intel: move emgd-driver-bin_1.8 to common) somehow mistakenly removed the unrelated

From: Tom Zanussi <tom.zanussi@...> Trying to build rt images for crownbay and fri2, I ran in to a few build problems - this patchset fixes them up. The following changes since commit

Fix obvious typoes in .bb files for libzypp and sat-solver packages, and update the HOMEPAGE for sat-solver to refer to the sat-solver home page itself, rather than the libzypp home

filed a bug on sato-input. thanks!

i'm guessing it was exactly that -- a stale tarball i didn't realize i was picking up. since now i can't reproduce so i'm going to forget about it unless it happens again. coming shortly. rday

Probably that a stale tarball was still on your system. Can you tell me how you're proceeding when the fetch has failed? Do you cleanall before trying again? Sounds like we have a bug to fix in here

never mind, just cleared *everything* out and tried again and it worked. mystery. in any event, there's a minor typo in the sat-solver_git.bb file: HOMEPAGE =

I cannot reproduce this on my F16 workstation here. I recall similar issues in the past due to buggy tar on the host system, for which we added a tar native recipe. My system is fetching the tarball

Thanks for the info. As I'm very new to Yocto, I'd not know how to create local.conf to build for panda, even knowing that the kernel will support pandaboard. How would I go about configuring Yocto

The build time issue is known, we're doing more work (building more things) in 1.1 - however, reducing build time is a primary goal and I expect there to be a reduction in build time by the time 1.2

We have a BitBake command to fetch all of the sources without actually doing the build: bitbake <target> -c fetchall i.e. bitbake core-image-sato -c fetchall OR bitbake world -c

I do want to point out that: 1.1 is 12 hours while 1.0 was 8 hours, using the same machine on the same network, not sure why. input under sato does not work, it's showing some non-English

It is a goal of the Yocto Project (and Open Embedded) that parallel building is full supported, and any identified bugs are fixed quickly. Enable parallel builds and your performance will be

sorry for the typo in my previous email. guess I need get a i7 and start to use parallel build again. is there a way that, when a release is made, all the related source tarballs can be download as

core2duo E7200 2.53Ghz 4GB 500GB 1 thread 1 parallel due to past experience I had from the past(parallel make did not work well reliably) thanks, xianghua

i ran into this a few weeks back, and i'm still having this grief. I'm running: $ bitbake -c fetchall core-image-sato and it's perpetually failing trying to fetch the sat-solver package. based on

We also test 1.1 on a 4-core Core i7 machine with 4GB memory. The build time is about 120 minutes. The detailed test result and configuration is on https://wiki.yoctoproject.org/wiki/Performance_Test.

What machine are you using (amount of ram, disk space, and cpu cores)? What configuration did you set for parallel builds? I can build 1.1 on an 8 core i7 system w/ 8 GB of ram, set with

when I built 1.0 out of the box, it took 7 hours. on the same machine/network, yocto 1.1 took a full 12 hours, not sure what happened to cause this nearly doubled build time. after the default