[yocto] arm-poky-linux-gnueabi-gcc: Command not found

[Craig McQueen]

ravikiran j wrote:
> 
> I am trying to build the linux kernel for odorid-xu3 board but i am getting following errors for
> bitbake linux-stable
> 
> 
> DEBUG: Executing shell function do_compile
> NOTE: make -j 4 HOSTCC=gcc  HOSTCPP=gcc  -E zImage CC=arm-poky-linux-gnueabi-gcc   -fuse-ld=bfd LD=arm-poky-linux-gnueabi-ld.bfd
> ERROR: oe_runmake failed
> /home/mistral/yocto1/poky/build-xfce/tmp/work-shared/odroid-xu3/kernel-source/scripts/gcc-version.sh: line 25: arm-poky-linux-gnueabi-gcc: command not found
> /home/mistral/yocto1/poky/build-xfce/tmp/work-shared/odroid-xu3/kernel-source/scripts/gcc-version.sh: line 26: arm-poky-linux-gnueabi-gcc: command not found
> make[2]: arm-poky-linux-gnueabi-gcc: Command not found
> make[2]: arm-poky-linux-gnueabi-gcc: Command not found
>   GEN     ./Makefile
> scripts/kconfig/conf  --silentoldconfig Kconfig
> /home/mistral/yocto1/poky/build-xfce/tmp/work-shared/odroid-xu3/kernel-source/scripts/gcc-version.sh: line 25: arm-poky-linux-gnueabi-gcc: command not found
> /home/mistral/yocto1/poky/build-xfce/tmp/work-shared/odroid-xu3/kernel-source/scripts/gcc-version.sh: line 26: arm-poky-linux-gnueabi-gcc: command not found
> make[2]: arm-poky-linux-gnueabi-gcc: Command not found
> make[2]: arm-poky-linux-gnueabi-gcc: Command not found
>   CHK     include/config/kernel.release
> make[2]: arm-poky-linux-gnueabi-gcc: Command not found
> make[2]: arm-poky-linux-gnueabi-gcc: Command not found
>   GEN     ./Makefile
> 
> 
>  Using /home/mistral/yocto1/poky/build-xfce/tmp/work-shared/odroid-xu3/kernel-source as source for kernel
> make[2]: arm-poky-linux-gnueabi-gcc: Command not found
> make[2]: arm-poky-linux-gnueabi-gcc: Command not found
>   HOSTCC  scripts/pnmtologo
>   HOSTCC  scripts/kallsyms
>   CC      scripts/mod/empty.o
> /bin/sh: 1: arm-poky-linux-gnueabi-gcc: not found
> /home/mistral/yocto1/poky/build-xfce/tmp/work-shared/odroid-xu3/kernel-source/scripts/Makefile.build:293: recipe for target 'scripts/mod/empty.o' failed
> make[4]: *** [scripts/mod/empty.o] Error 127
> /home/mistral/yocto1/poky/build-xfce/tmp/work-shared/odroid-xu3/kernel-source/scripts/Makefile.build:544: recipe for target 'scripts/mod' failed
> make[3]: *** [scripts/mod] Error 2
> make[3]: *** Waiting for unfinished jobs....
>   HOSTCC  scripts/dtc/dtc.o
>   HOSTCC  scripts/dtc/flattree.o
>   HOSTCC  scripts/dtc/fstree.o
>   HOSTCC  scripts/dtc/data.o
>   HOSTCC  scripts/dtc/livetree.o
>   HOSTCC  scripts/dtc/treesource.o
>   HOSTCC  scripts/dtc/srcpos.o
>   HOSTCC  scripts/dtc/checks.o
>   HOSTCC  scripts/dtc/util.o
>   SHIPPED scripts/dtc/dtc-lexer.lex.c
>   SHIPPED scripts/dtc/dtc-parser.tab.h
>   SHIPPED scripts/dtc/dtc-parser.tab.c
>   HOSTCC  scripts/dtc/dtc-lexer.lex.o
>   HOSTCC  scripts/dtc/dtc-parser.tab.o
>   HOSTLD  scripts/dtc/dtc
> /home/mistral/yocto1/poky/build-xfce/tmp/work-shared/odroid-xu3/kernel-source/Makefile:560: recipe for target 'scripts' failed
> make[2]: *** [scripts] Error 2
> Makefile:150: recipe for target 'sub-make' failed
> make[1]: *** [sub-make] Error 2
> Makefile:24: recipe for target '__sub-make' failed
> make: *** [__sub-make] Error 2
> WARNING: exit code 1 from a shell command.
> ERROR: Function failed: do_compile (log file is located at /home/mistral/yocto1/poky/build-xfce/tmp/work/odroid_xu3-poky-linux-gnueabi/linux-stable/4.9.13+gitAUTOINC+f3329efb7f-r0/temp/log.do_compile.15577)
> what is the problem and how to solve this problem ?

I had a similar problem. I was building a kernel for BeagleBone Black, using meta-ti for kernel. I'm currently using Yocto poky morty branch.

In my case, the problem was that I had a .bbappend file for the kernel, and in the .bbappend file was mistakenly overwriting DEPENDS. It had a line such as:

DEPENDS_beaglebone += "my-initramfs-image"

But that is an incorrect way to append to DEPENDS for the specific machine. Using DEPENDS_machinename += "..." is the wrong way to do it, because the += operation doesn't pull in the existing DEPENDS values, but an empty DEPENDS_machinename value. Then after that, the DEPENDS_machinename overrides the kernel recipe's plain DEPENDS, so the kernel DEPENDS ends up missing all the build dependencies.

It should instead be one of:

DEPENDS += "my-initramfs-image"
Or:
DEPENDS_append_beaglebone = " my-initramfs-image"

I don't know if your problem has the same cause, but I thought I should describe my problem in case it's related.

You can check the DEPENDS definition that bitbake is using by running bitbake on your kernel recipe with the -e option.

-- 
Craig McQueen