**** BEGIN LOGGING AT Sun Apr 22 03:00:05 2018 Apr 22 03:08:29 New news from stackoverflow: Yocto do_kernel_metadata failed with custom BSP Apr 22 18:44:37 quick question; I was about to create riscv-compiler yocto packaging. first hit seems to be 'configure: error: cannot run C compiled programs' from 'populate_sdk' for the package. this seems to be a valid finding, 'x86_64-pokysdk-linux-gcc' produces output that requests ld.so from /opt/poky, which logically does not exit while building the sdk. Apr 22 18:49:14 chicken-and-the-egg kind of thing, it would probably run if I had the sdk installed to begin with. but, it is still supposed to be making that sdk... Apr 22 18:58:36 so in other words, while the sdk is building stuff produced by 'x86_64-pokysdk-linux-gcc' is not runnable unless there was sdk installed on the machine to begin with. bug or a feature ..? Apr 22 19:16:13 /home/yocto/poky/build/tmp/work/x86_64-nativesdk-pokysdk-linux/nativesdk-riscv-tools/0.1-r0/riscv-tools-0.1/build$ x86_64-pokysdk-linux-gcc --sysroot=/home/yocto/poky/build/tmp/work/x86_64-nativesdk-pokysdk-linux/nativesdk-riscv-tools/0.1-r0/recipe-sysroot t.c Apr 22 19:16:27 file ./a.out Apr 22 19:16:27 ./a.out: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /opt/poky/2.4.2/sysroots/x86_64-pokysdk-linux/lib/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=38816e567eb71dd1640744a8552807912dbe038e, not stripped Apr 22 19:18:48 beyond my comprehension how that was supposed to run during the build unless there was a sdk installed before starting. I guess it was supposed to find this somehow; /home/yocto/poky/build/tmp/work/x86_64-nativesdk-pokysdk-linux/nativesdk-riscv-tools/0.1-r0/recipe-sysroot/opt/poky/2.4.2/sysroots/x86_64-pokysdk-linux/lib/ld-linux-x86-64.so.2 **** ENDING LOGGING AT Mon Apr 23 03:00:11 2018