Fair enough. And I should mention that the error I reported occurs on Ubuntu 10.04. It's not like I wasn't warned. :-} WARNING: Host distribution "Ubuntu 10.04 LTS" has not been validated with

I was told that I hit the server at a busy time thus causing the fetch to fail. I just re-ran it and ran error free. I was also told this was a rare occurrence but it does happen. Scott

Something was bugging me about this, so I dug up my notes. I was wrong when I said switching to denzil fixed my problem---it did NOT. I simply cannot untar/uncompress the perl archive from CPAN with

I'm new to Yocto, but I've seen similar errors that seem to be due to differences in the version of tar on the build server. Everything's fine on this machine: good% tar --version tar (GNU tar)

I am running through the build example for the QS and hit a failure when trying to access git://git.yoctoproject.org/libowl;protocol=git. I started with the tarball here:

I have recipes for if 3.3 actually I will publish it after 1.3 release it needs some fine touches

Hi all, Are there any plans for Yocto to includePython 3.2.3 as an alternative to the Python 2.7.3 recipes? I mightneed to use it at some point, so I was wondering if it was on the

Yeah, looks like the other SRC_URIs do that, but it's missing from that SRC_URI - I just pushed a fix for this one to meta-intel/master. Tom

Hi, I have a recipe that uses GNU autoopts, which generates a dependency on libopts. This is the library that is required for any package using autoopts to compile. GNU autoopts is a tool that is

That's a bug alright. It seems the overall SRC_URI of linux-yocto is overwritten by meta-cedartrail layer, when included. Should be fixed by using SRC_URI_cedartrail instead. -- Mihai Lindner

Hi, If I add meta-intel and meta-cedartrail to my bblayers, when I try and do an atom-pc build (which I thought should still work, right?) I get the following error: NOTE: Error during finalise

Hello, Yes they can be separated from the Medium bugs (now they are all counted together). Also if we want their “weight” to differ from the Medium ones we can change that too (I would suggest

Hi Joy and Kishore, 2 things you need to fix/check: 1. Please extract your toolchain to /opt/poky, basically go to your root directory “/” and run “sudo tar –xvjf path to your

Copying to the Yocto Mailing list. Is anyone familiar with Eclipse tool and Yocto Project ADT? Thanks Kishore.

I just noticed that the open bug trends don't call out the medium+ bugs. Can these be added? From: <Serban>, Laurentiu Serban <laurentiu.serban@...<mailto:laurentiu.serban@...>> Date:

Dear Chris, In message <CABcZANmPe_D+GPWxnkVZCmE9ti011ZDSXxPix8ztW4vrdYiyZA@...> you wrote: Sorry, but I don't get how this is supposed to work. I have an incompatible change, and

This is wrong. A compatibility break in bblayers.conf is *extremely* rare. Wrong. The user has to know that they may need to change their bblayers.conf to match the upstream structure. If it didn't

Dear Paul, In message <224780988.1nyHnvScgz@helios> you wrote: Well, the comment in "meta-yocto/conf/bblayers.conf.sample" says: # LAYER_CONF_VERSION is increased each time

The rationale is for this specific increase is this: if you previously had meta-yocto in your existing bblayers.conf, since the reference BSP parts of meta-yocto were split out into meta-yocto-bsp

They're both set exactly the way they should be. You're only affected by the bblayers compatibility change if you use poky, as far as I'm aware. -- Christopher Larson