could you double confirm the link below is used in your side? Ideally the gnu mirror should be used, e.g. ftp://ftp.gnu.org/gnu/gcc/gcc-4.5.1/gcc-4.5.1.tar.bz2 in my log though it’s 4.5.1 If the upstr

could you try manually download the tar ball from the link, and then copy to the /home/rsaxena/poky-4.0-build/downloads/? Thanks Kevin

I think we should extend checksum to cover local files/patches, instead of just recipe variables. This way old sstate cache will be automatically invalided due to different checksum from /etc/interfac

Thanks for the catch-up. I do remember that you dig it out but not realize related here. :-) Thanks Kevin

This is a known issue in 0.9. the switch from ipk to rpm leaves some temporary files in the final ext3 rootfs, which results the large size. This configuration option only works when it exceeds the si

Yes. Poky.git is a repo which contains a bunch of branches. One simple way you can verify is to use "git branch", and if "*master" is shown then you're using the master branch. If it still doesn't wor

Yes, it's make 3.82 related. My gut-feeling is that FC12 should have an older version which ends up wrong here. :-) OK, I remembered that there're a series of patches to make FC14 happy after Laverne

The make-native is required on Fedora14. So you don't need that step and Instead you could directly: Bitbake poky-image-sato Btw, could you post your errors? For native packages, yes the host compiler

Hi, Dave, Yes, LSB contains cron. I talked to Jiajun about choice of the profile. SDK profile simplifies QA’s test effort since it runs on both Qemu and real hardware, while LSB profile is not suitabl

Hi, all, I’d like to give a quick update about current LTP status. For detail, please check out: https://wiki.yoctoproject.org/wiki/LTP_result Generally LTP is for desktop compliance and not strictly

the mirror is only reached if there's no response from original SRC_URI link. In your case, the original link does work... which however provides a broken tar ball. From poky p.o.v, the do_fetch task

I've sent out the SRC_URI fixes to use correct Savannah site. BTW, if the mirror site is down, you should still get a correct tar ball from pre-configured poky mirrors (pokylinux.org, ...). Please let

yes, it's very likely that the file you downloaded from the mirror is broken. You can either change the SRC_URI in the acl*.bb to the real Savannah link, or download it manually and then copy to the p

Beth, thanks for sharing your observations and suggestions which are great. I think this is not true. Current guideline for distro team is to make incremental builds for all archs and make a full buil

Hi, all, I just create a new wiki page to track LTP status for Yocto Project: https://wiki.yoctoproject.org/wiki/LTP_result Embedded Linux distribution is unlike a typical desktop Linux, because it's

It's normal. There're several reasons for that. One is the debug symbols. The other is that Yocto implements build tasks in staged way to avoid interference among tasks, which results in multiple copi

I think the both. :-) This is always being a tradeoff in all distributions. There's no simple guideline whether there's severe risk to upgrade to a latest release, and I think the one general rule is

I'm kind of surprised when seeing this data, as I thought we have upgraded more than 110 recipes. Then distro team gathered just now to understand whether there's anything mismatch. The major point ca

Hi, all, I start looking into our LTP failures now and get some cursory picture. ( http://bugzilla.pokylinux.org/show_bug.cgi?id=169 ) I tried qemux86 sato image from latest M2 build, and there're in

Yes, SDK is generated from the distro metadata, which however doesn't prevent SDK as a standalone component to have its own version variable. We can have: SDK_VERSION = ${DISTRO_VERSION} or, SDK_VERSI