Bug 12162 - ERROR: do_kernel_metadata: Could not locate BSP definition
Summary: ERROR: do_kernel_metadata: Could not locate BSP definition
Status: RESOLVED FIXED
Alias: None
Product: Meta-yocto
Classification: Build System, Metadata & Runtime
Component: meta-yocto (show other bugs)
Version: 2.4
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 2.5 M1
Assignee: Saul Wold
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2017-10-03 13:26 UTC by Robert Berger
Modified: 2017-12-11 00:59 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know


Attachments
sample kernel recipe (1.82 KB, application/octet-stream)
2017-11-15 17:16 UTC, Robert Berger
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Berger 2017-10-03 13:26:59 UTC
on a custom kernel:

bitbake linux-yocto-custom -c menuconfig

NOTE: Started PRServer with DBfile: /tmp/yocto-autobuilder/yocto-autobuilder/yocto-worker/poky-custom-rocko-multi-v7-core-image-minimal/build/cache/prserv.sqlite3, IP: 127.0.0.1, PORT: 33313, PID: 27012
Loading cache: 100% |###########################################################################################################################| Time: 0:00:00
Loaded 1278 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION        = "1.35.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "universal"
TARGET_SYS        = "arm-poky-linux-gnueabi"
MACHINE           = "imx6q-phytec-mira-rdk-nand-bsp"
DISTRO            = "poky"
DISTRO_VERSION    = "2.4"
TUNE_FEATURES     = "arm armv7a vfp neon"
TARGET_FPU        = "softfp"
meta
meta-poky
meta-yocto-bsp    = "2017-10-02-rocko-2.4-pre-release:e632745c4e7a39f5461a23a99e72036281c56917"
imx6q-phytec-mira-rdk-nand-bsp = "master:0e7bbb3e6e35e0388864e9c8bce1dda22da30872"

Initialising tasks: 100% |######################################################################################################################| Time: 0:00:00
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: linux-yocto-custom-4.9.44+gitAUTOINC+a97a16f18c-r0 do_kernel_metadata: Could not locate BSP definition for imx6q-phytec-mira-rdk-nand-bsp/standard and no defconfig was provided
NOTE: Tasks Summary: Attempted 344 tasks of which 334 didn't need to be rerun and all succeeded.

Summary: There was 1 ERROR message shown, returning a non-zero exit code.


Error was ignored?
Comment 1 Richard Purdie 2017-10-05 15:01:01 UTC
I suspect some cases of bb.error() need to be bb.fatal() in the bbclasses.
Comment 2 Robert Berger 2017-11-15 17:16:04 UTC
Created attachment 4125 [details]
sample kernel recipe

This also happens after the 2.4 release and the point is it's right.
There is no defconfig and there are also no kernel metadata since I want to use an in tree kernel config.
Comment 3 Robert Berger 2017-11-15 17:17:16 UTC
I thought those lines would do the trick:

# Let's try an in-tree defconfig:
KERNEL_DEFCONFIG_imx6q-phytec-mira-rdk-nand-bsp ?= "multi_v7_defconfig"
KBUILD_DEFCONFIG_imx6q-phytec-mira-rdk-nand-bsp ?= "multi_v7_defconfig"
KCONFIG_MODE="--alldefconfig"
Comment 4 Saul Wold 2017-11-29 03:16:57 UTC
Robert, is it possible you have a "defconfig" file on the $WORKDIR that matches the KCONFIG_DEFCONFIG setting?  I think I found part of the problem is that the $sccs is not set if the KCONFIG_DEFCONFIG == $WORKDIR/defconfig and we should really be setting $sccs in both cases.

We might also want to change the bberror to bbfatal in this case.
Comment 5 Robert Berger 2017-11-29 20:51:47 UTC
Hi,

I don't quite understand what defconfig that should be.

Just a dummy file, or the real thing?

I want to use multi_v7_defconfig like[1] and apply config fragments on top of it. Like this I can move back and forth between kernel versions quite easily. Just need to change the commit id like here[2]

[1] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/tree/arch/arm/configs/multi_v7_defconfig?h=v4.14.2

[2] https://github.com/RobertBerger/meta-mainline/tree/rocko-training-v4.9.x/multi-v7-ml/recipes-kernel/linux

If you like I can try to add to my kernel recipe something which copies the multi_v7_defconfig wherever you would like to find it and rename it to defconfig. 

Is this what you want? multi_v7_defconfig to $WORKDIR/defconfig?