Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: Tom Rini <trini@konsulko.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] image_types: Fix bmaptool support for RSS
Date: Fri, 29 Sep 2017 17:21:02 +0300	[thread overview]
Message-ID: <20170929142102.int56ejorufnkh4v@linux.intel.com> (raw)
In-Reply-To: <20170929123652.GV3112@bill-the-cat>

On Fri, Sep 29, 2017 at 08:36:52AM -0400, Tom Rini wrote:
> On Fri, Sep 29, 2017 at 02:16:21PM +0300, Ed Bartosh wrote:
> > On Wed, Sep 27, 2017 at 01:00:09PM -0400, Tom Rini wrote:
> > > With RSS we need to ensure that when making a bmap image that the
> > > python3 that we created is found via /usr/bin/env rather than the host
> > > python3.  Otherwise we're relying on the build host to have bmaptool
> > > support installed.
> > > 
> > > Signed-off-by: Tom Rini <trini@konsulko.com>
> > > ---
> > > I played around with a few ways to try and fix this problem, and this
> > > was the best I could come up with.  Once this is in we need this in pyro
> > > as well as it's broken there too.
> > > ---
> > >  meta/classes/image_types.bbclass | 3 +++
> > >  1 file changed, 3 insertions(+)
> > > 
> > > diff --git a/meta/classes/image_types.bbclass b/meta/classes/image_types.bbclass
> > > index 61dca626311e..3ff960e3a889 100644
> > > --- a/meta/classes/image_types.bbclass
> > > +++ b/meta/classes/image_types.bbclass
> > > @@ -311,3 +311,6 @@ DEPLOYABLE_IMAGE_TYPES ?= "hddimg iso"
> > >  # The IMAGE_TYPES_MASKED variable will be used to mask out from the IMAGE_FSTYPES,
> > >  # images that will not be built at do_rootfs time: vmdk, vdi, qcow2, hdddirect, hddimg, iso, etc.
> > >  IMAGE_TYPES_MASKED ?= ""
> > > +
> > > +# bmap requires python3 to be in the PATH
> > > +EXTRANATIVEPATH += "${@'python3-native' if d.getVar('IMAGE_FSTYPES').find('bmap') else ''}"
> > 
> > +1
> > 
> > Would ...find('.bmap') be a bit more safe?
> 
> Could be.  Do I need to v2 or can someone just fix up while applying?

Please send v2.

--
Regards,
Ed


  reply	other threads:[~2017-09-29 14:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-27 17:00 [PATCH] image_types: Fix bmaptool support for RSS Tom Rini
2017-09-27 17:10 ` Burton, Ross
2017-09-27 17:52   ` Tom Rini
2017-09-27 19:34     ` Tom Rini
2017-09-27 21:01 ` Khem Raj
2017-09-27 21:53   ` Tom Rini
2017-09-27 22:14     ` Khem Raj
2017-09-27 22:17       ` Tom Rini
2017-09-28  4:38         ` Khem Raj
2017-09-28 14:13 ` Ed Bartosh
2017-09-28 14:53   ` Tom Rini
2017-09-29 11:16 ` Ed Bartosh
2017-09-29 12:36   ` Tom Rini
2017-09-29 14:21     ` Ed Bartosh [this message]
2017-09-29 14:28 ` [PATCHv2] " Tom Rini
2017-10-02  9:59   ` Ed Bartosh

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=20170929142102.int56ejorufnkh4v@linux.intel.com \
    --to=ed.bartosh@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=trini@konsulko.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