From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Tomasz Dziendzielski <tomasz.dziendzielski@gmail.com>,
openembedded-core@lists.openembedded.org
Cc: Jon Mason <Jon.Mason@arm.com>
Subject: Re: [OE-core] [PATCH v2] bitbake: Don't treat mc recipe (Midnight Commander) as a multiconfig target
Date: Sat, 30 Jan 2021 08:58:07 +0000 [thread overview]
Message-ID: <70cd3945856eb783c7239fd716eeea39b127e773.camel@linuxfoundation.org> (raw)
In-Reply-To: <20210128172313.7681-1-tomasz.dziendzielski@gmail.com>
On Thu, 2021-01-28 at 18:23 +0100, Tomasz Dziendzielski wrote:
> When we run `devtool build mc` recipe's task dependencies are expanded
> to "mc:do_populate_sysroot" where "mc" name is treated as multiconfig
> and "do_package_sysroot" as multiconfigname.
>
> > ERROR: Multiconfig dependency mc:do_populate_sysroot depends on
> > nonexistent multiconfig configuration named do_populate_sysroot
>
> Signed-off-by: Tomasz Dziendzielski <tomasz.dziendzielski@gmail.com>
>
> --- skipped change in showEnvironment() to keep "bitbake -e" working
> ---
bitbake patches need to go to the bitbake-devel list.
I did put this into testing anyway and it triggered errors in several
selftests:
bitbake-selftest:
https://autobuilder.yoctoproject.org/typhoon/#/builders/87/builds/1792/steps/11/logs/stdio
and oe-selftest:
https://autobuilder.yoctoproject.org/typhoon/#/builders/87/builds/1792/steps/14/logs/stdio
(these occurred in all the selftest builds but I've just linked to one).
Cheers,
Richard
next prev parent reply other threads:[~2021-01-30 8:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 17:23 [PATCH v2] bitbake: Don't treat mc recipe (Midnight Commander) as a multiconfig target Tomasz Dziendzielski
2021-01-30 8:58 ` Richard Purdie [this message]
2021-01-30 11:52 ` [OE-core] " Tomasz Dziendzielski
[not found] ` <165F0294B6476D79.25477@lists.openembedded.org>
2021-01-30 16:57 ` Tomasz Dziendzielski
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=70cd3945856eb783c7239fd716eeea39b127e773.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=Jon.Mason@arm.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=tomasz.dziendzielski@gmail.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