> From: Ross Burton > > Okaaaay. So what version of oe-core or poky are you using > that is providing the guile-native? Having autogen-native r3 > implies some revision of master post-danny, as danny (1.3) > only has autogen-native r2. Either way, both Danny and master > have guile-native 2.0.6.
They're both current within the last few weeks. However, a bit of history: My goal was to add Samba, which is contained in the meta-oe layer of meta-openembedded, which also required adding the meta layer of openembedded-core. But I initially used the master branch, got errors, and someone else told me I needed to use the danny branch. So it is possible that something is lying around from when I first tried the master branch. > What are you exact layers and versions? I'm not > understanding why you're not getting the guile-native that > must be present alongside your autogen-native (as I fixed > guile and then fixed autogen in the same day). My layers are poky-danny-8.0/meta poky-danny-8.0/meta-yocto poky-danny-8.0/meta-yocto-bsp poky-danny-8.0/meta-intel poky-danny-8.0/meta-intel/meta-cedartrail poky-danny-8.0/openembedded-core/meta poky-danny-8.0/meta-openembedded/meta-oe where the last two are not part of poky-danny-8.0, but were fetched separately from OpenEmbedded's git server, and the rest came from a couple of tarballs from the Yocto site. I'm not sure how to find specific version info on these, but like I said, they're all from the last few weeks. Do I need to clean something out, or should I nuke the build tree and start over, now that I've got the right OE branch? By the way, since you're from Intel, why the hell are they discontinuing the Atom D2700? -- Ciao, Paul D. DeRocco Paul mailto:pdero...@ix.netcom.com _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
