From: "Anuj Mittal" <anuj.mittal@intel.com>
To: "steven.monsees@baesystems.com" <steven.monsees@baesystems.com>,
"yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>
Subject: Re: [yocto] #yocto #kernel "yocto-check-layer"
Date: Wed, 10 Feb 2021 15:35:16 +0000 [thread overview]
Message-ID: <220d0d7cb6d00c2b105a71ea9402575e42e54cb8.camel@intel.com> (raw)
In-Reply-To: <MADEUP.1662676ABE100B46.25203@lists.yoctoproject.org>
On Wed, 2021-02-10 at 13:55 +0000, Monsees, Steven C (US) via
lists.yoctoproject.org wrote:
>
> Mb build was setup and done under one layer, with “distro” and “bsp“
> at the same layer, I wanted to split them up into separate layers
> inorder to better conform to the Yocto standard…. (Note my kernel
> builds and runs correctly when split or not split)
>
> When not split “Yocto-check-layer” calls me out for having “distro”
> and “bsp” in same layer, when I split them I am seeing the following
> for each new layer:
>
> Can someone explain the errors the script is reporting and how to
> resolve (these are not seen build the split or non-split images) ?
>
> 08:43 smonsees@yix490031
> /disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-
> limws/builds/sbcb-default>yocto-check-layer
> /disk0/scratch/smonsees/yocto/workspace_3/poky/../meta-bae/meta-
> limws/meta-intel/meta-intel-bsp
> INFO: Detected layers:
> INFO: meta-intel-bsp: LayerType.BSP,
> /disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/meta-
> intel/meta-intel-bsp
> INFO:
> INFO: Setting up for meta-intel-bsp(LayerType.BSP),
> /disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/meta-
> intel/meta-intel-bsp
> INFO: Getting initial bitbake variables ...
> INFO: Getting initial signatures ...
> INFO: Generating signatures failed. This might be due to some parse
> error and/or general layer incompatibilities.
> Command: BB_ENV_EXTRAWHITE="$BB_ENV_EXTRAWHITE BB_SIGNATURE_HANDLER"
> BB_SIGNATURE_HANDLER="OEBasicHash" bitbake -S none world
> Output:
> Parsing recipes...done.
> Parsing of 2450 .bb files complete (0 cached, 2450 parsed). 3645
> targets, 91 skipped, 0 masked, 0 errors.
> NOTE: Resolving any missing task queue dependencies
> ERROR: Nothing RPROVIDES 'shim' (but
> /disk0/scratch/smonsees/yocto/workspace_3/poky/meta/recipes-
> core/packagegroups/packagegroup-base.bb RDEPENDS on or otherwise
> requires it)
> NOTE: Runtime target 'shim' is unbuildable, removing...
> Missing or unbuildable dependency chain was: ['shim']
> ERROR: Required build target 'meta-world-pkgdata' has no buildable
> providers.
> Missing or unbuildable dependency chain was: ['meta-world-pkgdata',
> 'packagegroup-base', 'shim']
It looks like this packagegroup has a RDEPENDS on "shim" while the code
can't find the recipe. If that RDEPENDS is correct, this layer probably
needs to add a LAYERDEPENDS on a layer that has this recipe in
layer.conf.
Thanks,
Anuj
prev parent reply other threads:[~2021-02-10 15:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 13:55 #yocto #kernel "yocto-check-layer" Monsees, Steven C (US)
2021-02-10 15:17 ` Monsees, Steven C (US)
2021-02-10 20:24 ` [yocto] " Monsees, Steven C (US)
2021-02-10 15:35 ` Anuj Mittal [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=220d0d7cb6d00c2b105a71ea9402575e42e54cb8.camel@intel.com \
--to=anuj.mittal@intel.com \
--cc=steven.monsees@baesystems.com \
--cc=yocto@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.