Using hardy (8.04) and building minimal image for qemuarm leads cc into busyloop. Quite likely a bug in gcc-4.2.4 (Ubuntu 4.2.4-1ubuntu4). Three hosts were tested: * x86_64 running 8.04 (mostly clean install) * i686 running 8.04 (vm, clean pristine install with all updates) * i686 running 10.04 (vm, clean pristine install with all updates) Both 8.04 end up in cc1 using 100% CPU without making any system calls (busyloop) indefinitely. The directory which gcc is building is libdwfl. 10.04/Lucid works without problems (newer gcc). Also, on x86_64 tested the same target using master, with same results, so issue is not 0.9/4.0-specific. Steps to recreate: 1. Get a clean 8.04 and do all updates 2. Using the yocto project quick start document, install the recommended packages. 3. Get and extract laverne-4.0 as per instructions. 4. Install python2.6 as per https://lists.yoctoproject.org/pipermail/yocto/2010-December/000447.html 5. source poky-laverne-4.0/poky-init-build-env poky-4.0-build (as per quick start) 6. The following modifications were done to local.conf: DL_DIR ?= /auto/oe-sources MACHINE ?= "qemuarm" SDKMACHINE ?= "i586" (for non-x86-64 targets) 6. bitbake elfutils-native-0.148-r1 7. Fix the 2 remaining issues that bitbake env check complains about (vm.mmap start, default shell) 8. elfutils-native-0.148-r1 9. Get a lot of coffee and come back to observe cc1 stuck at 100% Other things ruled out so far (changing these had no effect): * parallel builds / parallel threads * ccache * psyco * using master vs 0.9 tarball
Step 8 should read: 8. bitbake elfutils-native-0.148-r1
is there a hardy (8.04) system for me to use. All the systems I work on are Fedora.
I see the latest hardy is 8.04.4 LTS, does it happen on it ? I am about to install ubuntu on a system, just checking which is right ubuntu to install. Thanks, Nitin
Can not reproduce :( met python error with current poky master branch. $ bitbake elfutils Pseudo is not present but is required, building this first before the main build Sorry, python 2.6.0 or later is required for this version of bitbake
updated hardy gave me this: # python --version Python 2.5.2
So from python's point of view, the hardy distro is too old to run our bitbake. So is it worth going after the older distro for this bug ?
It's possible to get a working python also on Hardy. However, since Hardy on Desktop is coming to its end-of-life soon (end of security updates for desktop), maybe you're right to move this into obsolete (I'm ok with it).