From: "André Draszik" <git@andred.net>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] image.bbclass: also mask debugfs versions of masked images
Date: Mon, 12 Sep 2016 16:26:10 +0100 [thread overview]
Message-ID: <1473693970.22823.0.camel@andred.net> (raw)
In-Reply-To: <20160905083354.27655-1-git@andred.net>
ping
On Mo, 2016-09-05 at 09:33 +0100, André Draszik wrote:
> When IMAGE_GEN_DEBUGFS is enabled, and IMAGE_FSTYPES_DEBUGFS is left
> at its default (as suggested by local.conf.sample.extended),
> recipe parsing fails:
>
> bitbake kern-tools-native # or anything else for that matter
> ERROR: <poky.git>/meta/recipes-core/images/build-appliance-
> image_15.0.0.bb: No IMAGE_CMD defined for IMAGE_FSTYPES entry
> 'debugfs_vmdk' - possibly invalid type name or missing support class
> ERROR: Failed to parse recipe: <poky.git>/meta/recipes-
> core/images/build-appliance-image_15.0.0.bb
>
> Summary: There was 1 WARNING message shown.
> Summary: There were 2 ERROR messages shown, returning a non-zero exit
> code.
>
> i.e. bitbake doesn't even finish parsing...
>
> Since IMAGE_FSTYPES_DEBUGFS is based on IMAGE_FSTYPES, and
> since the build-appliance-image is setting IMAGE_FSTYPES
> to vmdk, image.bbclass/image_types.bbclass will be trying
> to build a debugfs_vmdk, causing the error, as this is not
> implemented.
>
> One solution to solving this problem could be as simple as
> adding a line
> IMAGE_FSTYPES_DEBUGFS_remove = "vmdk"
> to the build-appliance-image recipe, but that is very
> specific to the error encountered and carries the risk of
> the error being reintroduced in another recipe.
>
> Another solution could be to add 'debugfs_vmdk' to
> IMAGE_TYPES_MASKED in image-vm.bbclass, but again, this
> approach doesn't seem generic enough.
>
> None of the live and vm type images have an implementation
> for building a debugfs version, it doesn't seem to make
> sense to build debugfs versions of any of them anyway, and
> given IMAGE_TYPES_MASKED appears to be intended for those
> image types exclusively, it seems the right approach is to
> unconditionally also mask all debugfs_ flavours from
> IMAGE_TYPES_MASKED to achieve a generic solution.
>
> Do that so.
>
> Signed-off-by: André Draszik <git@andred.net>
> ---
> meta/classes/image.bbclass | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
> index 8c8b8a2..07bd2d6 100644
> --- a/meta/classes/image.bbclass
> +++ b/meta/classes/image.bbclass
> @@ -415,6 +415,7 @@ python () {
> d.appendVarFlag('do_image', 'vardeps', ' '.join(vardeps))
>
> maskedtypes = (d.getVar('IMAGE_TYPES_MASKED', True) or "").split()
> + maskedtypes = [dbg + t for t in maskedtypes for dbg in ("",
> "debugfs_")]
>
> for t in basetypes:
> vardeps = set()
prev parent reply other threads:[~2016-09-12 15:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-05 8:33 [PATCH] image.bbclass: also mask debugfs versions of masked images André Draszik
2016-09-12 15:26 ` André Draszik [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=1473693970.22823.0.camel@andred.net \
--to=git@andred.net \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox