From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: Ioan-Adrian Ratiu <adrian.ratiu@ni.com>
Cc: ken.sharp@ni.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2] wic/isoimage-isohybrid: check for grub-mkimage
Date: Wed, 4 Jan 2017 22:19:37 +0200 [thread overview]
Message-ID: <20170104201937.GA28348@linux.intel.com> (raw)
In-Reply-To: <20170104201255.GA28112@linux.intel.com>
On Wed, Jan 04, 2017 at 10:12:55PM +0200, Ed Bartosh wrote:
> On Wed, Jan 04, 2017 at 09:04:43PM +0200, Ioan-Adrian Ratiu wrote:
> > The isohybrid plugin uses grub-mkimage but doesn't make sure it gets built.
> > Add a check to avoid the following error:
> >
> > Error: A native program grub-mkimage required to build the image was not found (see details above).
> >
> > Wic failed to find a recipe to build native grub-mkimage. Please file a bug against wic.
> >
> > Signed-off-by: Ioan-Adrian Ratiu <adrian.ratiu@ni.com>
> > ---
> > scripts/lib/wic/plugins/source/isoimage-isohybrid.py | 5 +++++
> > 1 file changed, 5 insertions(+)
> >
> > diff --git a/scripts/lib/wic/plugins/source/isoimage-isohybrid.py b/scripts/lib/wic/plugins/source/isoimage-isohybrid.py
> > index 849fd8bea3..d616316d61 100644
> > --- a/scripts/lib/wic/plugins/source/isoimage-isohybrid.py
> > +++ b/scripts/lib/wic/plugins/source/isoimage-isohybrid.py
> > @@ -242,6 +242,11 @@ class IsoImagePlugin(SourcePlugin):
> > msger.info("Building mtools-native...\n")
> > exec_cmd("bitbake mtools-native")
> >
> > + # Make sure grub-mkimage is available in native sysroot
> > + if not os.path.isfile("%s/usr/bin/grub-mkimage" % native_sysroot):
> > + msger.info("Building grub-native...\n")
> > + exec_cmd("bitbake grub-native")
> > +
> > @classmethod
> > def do_configure_partition(cls, part, source_params, creator, cr_workdir,
> > oe_builddir, bootimg_dir, kernel_dir,
>
> Unfortunately this approach will not work if wic is run from bitbake.
>
> I'd suggest to simply add grub-native to NATIVE_RECIPES dictionary in
> scripts/lib/wic/utils/oe/misc.py
> It will make error message more informative and useful.
>
The same should probably be done with the rest of native tools called from
this module. It's better to avoid building them implicitly.
--
Regards,
Ed
next prev parent reply other threads:[~2017-01-04 20:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 19:04 [PATCH v2] wic/isoimage-isohybrid: check for grub-mkimage Ioan-Adrian Ratiu
2017-01-04 20:12 ` Ed Bartosh
2017-01-04 20:19 ` Ed Bartosh [this message]
2017-01-05 10:21 ` Ioan-Adrian Ratiu
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=20170104201937.GA28348@linux.intel.com \
--to=ed.bartosh@linux.intel.com \
--cc=adrian.ratiu@ni.com \
--cc=ken.sharp@ni.com \
--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