I don't think it is just the intel ones. All the BSPs I've looked at had this problem. The yocto-bsp also creates packages that add to the problem, as it's finished product adds files that end up in

From the perspective of a new, easily confused and overwhelmed user, I whole heartedly agree with the index entry. And now it makes sense why there is a PV to store version of a recipe.

The version of nfsd used in 3.4 kernels tries to upcall the new reboot-recovery daemon and gets stuck if it is not found. This causes client mounts to fail and prints the following error message

The new recovery mechanism used by nfs in 3.4 kernels is currently failing when building baryon against poky 1.3_M3. This workaround causes nfs to revert back to the old recovery mechanism. The issue

<paul.eggleton@...> wrote: Not that it matters in the grand scheme of things, but I would be in favour of switching the variable names. Consistency is as consistency does; if there's any

(I answered Scott privately by mistake - here's some feedback on-list) I'm in favor of mentioning the history somewhere, because the names do have a 'P' in them, and this is confusing

Rudolf, This is good feedback on the descriptions for the variable names Rudolf. I did try and clean things up there a bit. Thanks, Scott

I am not advocating changing the variable names. I know that this is a huge undertaking and prone to many problems. This probably one of the many legacy things people will have to live with and

I have tried to weed out the ambiguous use of "package" for this upcoming version of the manual set. I don't think I would want to suggest changing any of the "P*" type variable names in the code. I

No dispute there. The thing is, we no longer do that - we've fixed a number of references in the documentation, help text and error messages for this release so that "recipe" is used when that's

+1 I agree with Scott's definition. In the general Linux context a Package is a compilation of binaries, documentation, development files, etc. wrapped up in a format that can be used by a package

Paul, Thanks for the clarification on the host packages. Maybe I should rewrite "The Packages" section to use that term. That seems best. I guess the reason I wanted to explain the weird variable

Hi Scott, The thing is, this is actually the same meaning, we're just talking about packages for your host distribution rather than packages for the custom distro you're building - the concept is

This post will have some strong opinions and responses. But, I want to throw this out as a re-write of the term “Package” as defined in the YP Development Manual’s “Terms” section. I gave

Just to bring this full circle: I finally got the CRC error on my Ubuntu 10.04 build server to go away by adding the following line to /etc/apt/sources.list: deb http://archive.ubuntu.com/ubuntu

Oh! Didn't even think of that. :-% Looks like it's gzip: evadeflow% gzip -d perl-5.14.2.tar.gz gzip: perl-5.14.2.tar.gz: invalid compressed data--crc error Nice find! I'll see about updating my

Is it definitely tar that's the problem or gzip? This would suggest gzip: http://code.google.com/p/go/issues/detail?id=3443 Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre

My bad, sorry. (I really need to read more carefully.) Here's what I get when I add the missing lines: evadeflow% cat > temp.sh #!/bin/sh needtar=1 TARVERSION=`tar --version | head -n 1 | cut -d ' '

No, but the rest of the script (the bit following the blank line that you've omitted) is... I wanted to ensure that both the stripping out of the version and float_test were working.

To answer your questions... Yessir. evadeflow% cat pseudodone /home/evadeflow/projects/poky-git/build/tmp/sysroots/i686-linux/usr/bin Erm... that *specific* bit prints nothing when pasted into a