Bug 6781

Summary: There are no sanity check for /usr/bin/bc command
Product: [Build System, Metadata & Runtime] BSPs Reporter: Tautvydas <gtautvis>
Component: bsps-meta-xilinxAssignee: Alejandro Hernandez <alejandro.hernandez>
Status: RESOLVED FIXED QA Contact:
Severity: minor    
Priority: Low CC: bluelightning, bruce.ashfield, meta.layer.watcher, meta.watcher
Version: unspecified   
Target Milestone: 1.8   
Hardware: x86   
OS: x86_64   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Don't know

Description Tautvydas 2014-09-30 20:33:28 UTC 
There are no sanity check for /usr/bin/bc command. It occurs when compiling oe-core with meta-xilinx on system without bc package.

Log data follows:
| DEBUG: Executing shell function do_compile
| NOTE: make -j 8 uImage CC=arm-oe-linux-gnueabi-gcc  -mno-thumb-interwork -marm LD=arm-oe-linux-gnueabi-ld.bfd   UIMAGE_LOADADDR=0x8000
|   CHK     include/config/kernel.release
|   CHK     include/generated/uapi/linux/version.h
|   CHK     include/generated/utsrelease.h
| make[1]: `include/generated/mach-types.h' is up to date.
|   CALL    scripts/checksyscalls.sh
|   CHK     include/generated/compile.h
|   BC      kernel/timeconst.h
| /bin/sh: 1: bc: not found
| make[1]: *** [kernel/timeconst.h] Error 127
| make: *** [kernel] Error 2
| make: *** Waiting for unfinished jobs....
| make: *** wait: No child processes.  Stop.
| ERROR: oe_runmake failed
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_compile (log file is located at /home/xlnx/oe-core/build/tmp-glibc/work/zedboard_zynq7-oe-linux-gnueabi/linux-xlnx/3.14-xilinx+git2b48a8aeea7367359f9eebe55c4a09a05227f32b-r0/temp/log.do_compile.23077)
Comment 1 Paul Eggleton 2014-10-01 17:15:13 UTC 
We provide bc-native to resolve this in the core, but it appears for whatever reason that this was added to linux-yocto.inc rather than kernel.bbclass. Bruce, should we be moving the DEPENDS?
Comment 2 Bruce Ashfield 2014-10-01 17:35:18 UTC 
We can safely remove the DEPENDS. At the time we were only seeing
this on linux-yocto builds, so the change was kept focused to avoid
breaking any other builds.
Comment 3 Paul Eggleton 2014-10-02 09:00:39 UTC 
I assume you mean "move" rather than "remove"?