Not specifically. "bitbake -u hob" should let you see where things are at. Please keep in mind that its under active development at the moment and can be considered "alpha" quality but feedback is wel

Merged to master, thanks. Richard

I think we have all the pieces there but someone would have to connect them up... Cheers, Richard

I agree that the docs in master should reflect the code in master and that the docs on the bernard branch should be the ones which make the bernard references. Which or both can end up on the website

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 this c

The tune files (conf/machine/include/tune*) usually set the march and mcpu options which are added to CFLAGS. Does that provide the functionality you're looking for? Cheers, Richard

:) GMAE = GNOME Mobile and Embedded think cut down GNOME. At this point its a requirement, we'd like to relax that but it isn't possible right now. Cheers, Richard

Does strace show where its looking for it? Cheers, Richard

Merged to master, thanks. Richard

EXCLUDE_FROM_WORLD_pn-libmad = "1" should remove libmad from world builds. Cheers, Richard

I've not seen this before. You could run "file /home/ahaupt/yocto-git/build/tmp/sysroots/atom-pc/usr/lib/libgdbm.so.3.0.0" and check that its of the correct architecture since the invalid instruction

Sounds correct... Is this on a fresh clean build directory? You could also try "bitbake -c cleansstate python gdbm" on your existing build directory and retry "bitbake python" to see if its reproducib

This list is as good a place as any! :) Its relatively easy to arrange for a git repository. The main things we ask are that it has clearly defined maintainership (a clear maintainer and submission pr

So just to put what Bruce says into other words, there isn't any hard requirement to use linux-yocto but we are asking people to try it and if it doesn't work, at least tell us why. I understand trans

Just for reference, this is exactly what meta-intel intends to do. The released versions of the code there are based on a specific release of Yocto/OE-Core. When new BSPs are developed they are likely

The original criteria for what we included was: * One board per architecture * Should be available to a general developer in a relatively cost effective manner (sub $1000?) * Lets us test functionalit

Agreed, patch merged to master, thanks. Richard

FWIW, POKYMODE was replaced by TCMODE as part of the OE-Core changes. I'd be interested to know where we've missed the references to it and get to get those references fixed. Cheers, Richard

I'll explain on the condition that someone actually documents this ;-). TCMODE determines which of the files in meta/conf/distro/include/tcmode-* is used. It defaults to "default" and our default tool

Beth needs to take a look at that one I suspect. There is a fix in master to clean up the TARGET_ARCH* variables on x86_64. If we could follow that through into meta-intel it should resolve much of th