Richard/Saul, The hardware reference platforms need to be updated to the most recent linux-yocto changes in oe-core. The commit message has all the details: This is an update of the linux-yocto 3.0

Hi all, The overall open bug trend increased a lot during last 2 weeks. WDD number and Open Bug number are 819 and 164. QA began 1.2 M3 RC1 testing last week. Bug status of WW09 could be found on

i just finished doing a "bitbake core-image-minimal" for a beagleboard using the meta-ti layer, and having only to set a preferred version for udev. the build finished (albeit with a few

taking koen's advice to heart, should this discussion be happening on the meta-ti list? rday -- ======================================================================== Robert P. J. Day

One of the issues: https://lists.yoctoproject.org/pipermail/meta-ti/2012-February/000491.html I haven't tried if either 3.0 or a pending 3.1 update for Panda (from omapzoom/ti-ubuntu), resolve this

I'd like to know this myself because I need to build 64bit & 32bit toolchains (meta-toolchain) and currently I can only get both to build OK under Poky (yocto trunk) but it is 4.6.x and I need to work

Can you explain what the toolchain problems are and why the versions in oe-core don't work for meta-ti? -- ------------------------------------------------------------ Gary Thomas |

i *know* what i'm about to point out is an OE issue and i already quietly emailed koen, but when i tried the above (actually reordered my BBLAYERS entries first), i got a udev fetch error since it

Either way, meta-oe is still required for meta-ti due to toolchain issues...

um ... AFAICT, that .bbclass file is in meta-oe, not oe-core. and since i have meta-openembedded checked out, i simply copied the whole thing into my yocto tree, then tweaked my bblayers.conf file

Op 4 mrt. 2012, om 13:54 heeft Robert P. J. Day het volgende geschreven: First: -EWRONGLIST Second: Upstream calls it bonescript https://github.com/jadonk/bonescript

Apparently, they're still useful to people, so I think updating rather than retiring them makes more sense at this point (or they or something similar get merged into the Developer's guide? For now,

Yeah, just because poky appears in the URL doesn't mean we need to reference it beyond that. Yeah, definitely, I need to update these pages for for edison, which I'll do now that I know somebody's

just wandering through the yocto/poky reference manual, and it seems that some of the lists there are missing a few entries. first, in the images

Yeah, the example is pretty old, dating back to the 1.0 (bernard) release. Tom - it might be time to retire it, you think?

Signed-off-by: Robert P. J. Day <rpjday@...> --- diff --git a/documentation/dev-manual/dev-manual-start.xml b/documentation/dev-manual/dev-manual-start.xml index 2a93ec6..5627c82

yes, i know it's an editable wiki but i'd rather someone else make the changes just in case i'm misreading something. it's early, and there's only decaf in the place. this is bad. anyway, using

... much snipping below to get to the gist of it ... regardless of the fix, i would think that the proper name for that recipe file would be something like "beaglescript.bb" and

Oops, that's one more workaround I forgot to mention. This file is in OE-core, but not in poky. I made a local copy in my distro layer, but there must be a better way to handle it. --

not sure if you're suggesting i should now be able to build for, say, beagleboard with the meta-ti layer, but i cloned meta-ti into my yocto tree, added that layer to bblayers.conf, and tried to $