Bug 8808 - build-appliance: build core-image-minimal error under all ARCHs (2.1 M1)
Summary: build-appliance: build core-image-minimal error under all ARCHs (2.1 M1)
Status: RESOLVED FIXED
Alias: None
Product: Runtime
Classification: Build System, Metadata & Runtime
Component: build-appliance (show other bugs)
Version: 2.1
Hardware: x86 Multiple
: Undecided normal
Target Milestone: ---
Assignee: Cristian Iorga
QA Contact: Ke Zou
URL:
Whiteboard:
: 8817 (view as bug list)
Depends on:
Blocks:
 
Reported: 2015-12-15 02:07 UTC by Ke Zou
Modified: 2016-02-03 16:20 UTC (History)
7 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ke Zou 2015-12-15 02:07:46 UTC 
Build appliance image location:
autobuilder.yoctoproject.org/pub/releases/yocto-2.0_M1.rc1/build-appliance
(please ignore the naming mistake, this is actually a 2.1M1 build)

how to reproduce:
unzip build-appliance image
use vmplayer to play this virtual machine
build core-image-minimal image under any ARCH

error log:

Package: texinfo-dummy-native-1.0-r0
Task: do_install
Function Failed: do_install

DEBUG: Executing shell function do_install
cp: invalid option -- 'T'
BusyBox v1.24.1 (2015-12-08 11:24:31 GMT) multi-call binary.

Usage: cp [OPTIONS] SOURCE... DEST
WARNING: /home/builder/poky/build/tmp/work/x86_64-linux/texinfo-dummy-native/1.0-r0/temp/run.do_install.1011:1 exit 1 from
  cp -T "/home/builder/poky/build/tmp/work/x86_64-linux/texinfo-dummy-native/1.0-r0/template.py" "$FILENAME"
ERROR: Function failed: do_install (log file is located at /home/builder/poky/build/tmp/work/x86_64-linux/texinfo-dummy-native/1.0-r0/temp/log.do_install.1011)
Comment 1 Richard Purdie 2015-12-16 09:48:42 UTC 
Suspect that busybox priority replaced coreutils in this image. There is a patch on the mailing list which fixes this.
Comment 2 Richard Purdie 2015-12-17 11:57:23 UTC 
*** Bug 8817 has been marked as a duplicate of this bug. ***