From: "André Draszik" <git@andred.net>
To: Mark Hatle <mark.hatle@windriver.com>,
Ross Burton <ross.burton@intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] bitbake.conf: add default for IMAGE_FSTYPES_DEBUGFS
Date: Fri, 27 May 2016 15:42:13 +0100 [thread overview]
Message-ID: <1464360133.3815.7.camel@andred.net> (raw)
In-Reply-To: <a8f703f6-4b7b-d7f0-722f-df7caee70291@windriver.com>
On Fr, 2016-05-27 at 09:21 -0500, Mark Hatle wrote:
> On 5/27/16 5:54 AM, André Draszik wrote:
> > This doesn't work for me (at least on krogoth):
> >
> > ERROR: poky/meta/recipes-core/images/build-appliance-
> > image_14.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/meta/recipes-core/images/build-
> > appliance-image_14.0.0.bb
> >
> > I *instead* am using the attached patch successfully.
> >
> > Is anybody else facing the same issue?
>
> Ross's patch should have fixed this. It ensures that
> IMAGE_FSTYPES_DEBUGFS is
> always set to 'something'.
Yes, and now bitbake is looking for an IMAGE_CMD for debugfs_vmdk according
to the error message. Note that I didn't specify vmdk anywhere, my
IMAGE_FSTYPES is set to .tar.gz only.
> You should check if the patch has been applied to the "krogoth" branch.
I did apply it locally. For me, it only works if i revert Ross' patch and
apply my patch instead.
Cheers,
André
next prev parent reply other threads:[~2016-05-27 14:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-06 11:26 [PATCH] bitbake.conf: add default for IMAGE_FSTYPES_DEBUGFS Ross Burton
2016-05-06 11:40 ` Martin Jansa
2016-05-06 13:51 ` Mark Hatle
2016-05-06 14:13 ` Khem Raj
2016-05-27 10:54 ` André Draszik
2016-05-27 14:21 ` Mark Hatle
2016-05-27 14:42 ` André Draszik [this message]
2016-05-27 15:21 ` Mark Hatle
2016-05-27 20:42 ` André Draszik
2016-07-14 10:04 ` André Draszik
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=1464360133.3815.7.camel@andred.net \
--to=git@andred.net \
--cc=mark.hatle@windriver.com \
--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 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.