Building beagleboard poky-image-sato poky-image-minimal poky-image-sato-sdk failed: http://autobuilder.yoctoproject.org:8010/builders/nightly-external/builds/46/steps/shell_17/logs/stdio ERROR: runstrip: ''arm-poky-linux-gnueabi-strip' --remove-section=.comment --remove-section=.note '/srv/home/pokybuild/poky-slave/nightly-external/build/build/tmp/work/beagleboard-poky-linux-gnueabi/u-boot-v2010.12+r0+git1+c7977858dcf1f656cbe91ea0dc3cb9139c6a8cc8-r0/package/usr/bin/mkimage'' strip command failed NOTE: package findutils-4.4.2-r0: task do_package: Started NOTE: package u-boot-v2010.12+r0+git1+c7977858dcf1f656cbe91ea0dc3cb9139c6a8cc8-r0: task do_populate_sysroot: Succeeded NOTE: Running task 6975 of 7174 (ID: 2726, /srv/home/pokybuild/poky-slave/nightly-external/build/meta
I just built beagleboard poky-image-sato out of master and can't reproduce this.
I'm not sure why this caused a hard-stop, but looking at my logs.. there is a bug in the u-boot software: ERROR: runstrip: ''arm-poky-linux-gnueabi-strip' --remove-section=.comment --remove-section=.note '/home/mhatle/git/poky/build-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/u-boot-v2010.12+r0+git1+c7977858dcf1f656cbe91ea0dc3cb9139c6a8cc8-r0/package/usr/bin/mkimage'' strip command failed Looking at the file in question: /home/mhatle/git/poky/build-beagleboard/tmp/work/beagleboard-poky-linux-gnueabi/u-boot-v2010.12+r0+git1+c7977858dcf1f656cbe91ea0dc3cb9139c6a8cc8-r0/package/usr/bin/mkimage: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, stripped The file itself is a host executable, not built for the target. So there is an error in the u-boot package, it's attempting to install software that can't possibly run onto the target. (Shouldn't the insane checks catch this?)
http://git.pokylinux.org/cgit/cgit.cgi/poky/commit/?id=0f44acfd04ecc9709d5d47e7484f2481b3c64cd8
(In reply to comment #3) > http://git.pokylinux.org/cgit/cgit.cgi/poky/commit/?id=0f44acfd04ecc9709d5d47e7484f2481b3c64cd8 I don't see the issue in latest autobuilder logs.