Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: WARNING: Variable key %s (%s) replaces original key %s (%s).
Date: Mon, 5 Feb 2018 17:13:00 -0500	[thread overview]
Message-ID: <20180205221300.GG2786@denix.org> (raw)
In-Reply-To: <CAJTo0LYBFGxrHiDUK1FaJW3YB6hNZf4jiVTBgd7C2ONC9sq9XQ@mail.gmail.com>

On Mon, Feb 05, 2018 at 09:53:44PM +0000, Burton, Ross wrote:
> On 5 February 2018 at 18:21, Denys Dmytriyenko <denis@denix.org> wrote:
> 
> > Am I supposed to see bunch of these warnings (3 during parsing and 20 more
> > during build):
> >
> > WARNING: Variable key RDEPENDS_${KERNEL_PACKAGE_NAME}-base
> > (${KERNEL_PACKAGE_NAME}-image) replaces original key RDEPENDS_kernel-base
> > (kernel-devicetree).
> >
> >
> > From kernel.bbclass:
> >
> > # Allow machines to override this dependency if kernel image files are
> > # not wanted in images as standard
> > RDEPENDS_${KERNEL_PACKAGE_NAME}-base ?= "${KERNEL_PACKAGE_NAME}-image"
> >
> 
> That's your kernel recipe not liking the new multiple-name kernel classes,
> and if your problem is the same as oe-core's qemu* machines then this is
> the fix:
> 
> -RDEPENDS_kernel-base = ""
> +RDEPENDS_${KERNEL_PACKAGE_NAME}-base = ""

Ah, I see, thanks! I assume all other operations with that variable (like 
appends) would have to be changed similarly?

-- 
Denys


  reply	other threads:[~2018-02-05 22:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-05 18:21 WARNING: Variable key %s (%s) replaces original key %s (%s) Denys Dmytriyenko
2018-02-05 21:53 ` Burton, Ross
2018-02-05 22:13   ` Denys Dmytriyenko [this message]
2018-02-05 22:25     ` Burton, Ross
2018-02-06 10:00       ` Paul Eggleton

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=20180205221300.GG2786@denix.org \
    --to=denis@denix.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox