Hi Tom, For reference common include files are usually placed in conf/machine/include/. If that happens they also need non-generic suitably namespaced names, likely including "x86" or "ia32" in

Definitely. It was simply good fortune that it hadn't been used yet. And when something like you are doing arrives, we want to have it right. Just to have it right, is a good

True, I want to use this for configure toolchain properly: I'm looking at doing the following for when SPE is set: diff --git a/meta/recipes-devtools/gcc/gcc-common.inc

Signed-off-by: Robert P. J. Day <rpjday@...> --- i *think* this is what the author had in mind. diff --git a/documentation/yocto-project-qs/yocto-project-qs.xml

Signed-off-by: Robert P. J. Day <rpjday@...> --- diff --git a/documentation/yocto-project-qs/yocto-project-qs.xml b/documentation/yocto-project-qs/yocto-project-qs.xml index

sadly, i tossed the "bad" tarball, but i do recall that when i just tried to check the contents with "tar tvjf", it eventually reported unexpected EOF -- yes, i might have mentioned that earlier.

Do you still have the tarball with the bad md5sum? Can you diff the contents? Or was it simply a case of the bad tarball being truncated? Cheers, Paul -- Paul Eggleton Intel Open Source

while the problem has since gone away, something strange happened yesterday i figured i'd share. as a quick test, wanted to build core-image-sato so started with: $ bitbake -c fetchall

Hi all, I have been trying to build on Ubuntu 11.0.4. I think I have followed the online documentation correctly. I have also followed the wiki page, which is required for me, to set up the proxy

Acked-by: Bruce Ashfield <bruce.ashfield@...> Been meaning to change this for a while, the good news, is that the setting doesn't make any difference at the moment :) Cheers, Bruce

Fixes bug [YOCTO #1161] Fixes bug [YOCTO #773] This streamlines the routerstation pro configuration to remove options that are either unecessary or that are causing bugs. Also added to all branches

This is a repeat of the oe-core version of the patch, here's the duplicate text: The patch itself says it all, but here's an update to the 2.6.37 kernel that fixes a few issues. No sense sitting

The MPC8315E has a e300c3 core in it with 'classic' or normal PPC floating point. 'SPE' floating point is what exists on the e500v2 core. Signed-off-by: Kumar Gala <galak@...> ---

Here can work, or the oe-core lists. There are oe and oe-dev references for at least the e500v2 (that's what I've been working on importing .. slowly), and I haven't looked for others yet. So that's

From: Liping Ke <liping.ke@...> Since Hob only needes package dependency information, we can create a new version of package information retrieving methods, remove task dependency information,

From: Liping Ke <liping.ke@...> Since Hob only needes package dependency information, we can create a new version of package information retrieving methods, remove task dependency information,

may be meta/conf/machine/include. -- 倪庆亮 TEL: 13588371863 E-MAIL: niqingliang@... BLOG: http://niqingliang2003.wordpress.com

Where is the best place to ask questions and try and get support for adding some toolchain variations in? I'm wanting to add support in for a few different flavors of PPC that are not currently

From: Tom Zanussi <tom.zanussi@...> Have emenlow.conf use the common-bsp-* .inc files and remove the open-coded machine settings. Signed-off-by: Tom Zanussi <tom.zanussi@...> ---

From: Tom Zanussi <tom.zanussi@...> Have jasperforest.conf use the common-bsp-* .inc files and remove the open-coded machine settings. Signed-off-by: Tom Zanussi <tom.zanussi@...> ---