From: Tom Rini <trini@konsulko.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] image_types: Fix bmaptool support for RSS
Date: Wed, 27 Sep 2017 15:34:41 -0400 [thread overview]
Message-ID: <20170927193441.GA3112@bill-the-cat> (raw)
In-Reply-To: <20170927175218.GZ3112@bill-the-cat>
On Wed, Sep 27, 2017 at 01:52:18PM -0400, Tom Rini wrote:
> On Wed, Sep 27, 2017 at 06:10:58PM +0100, Burton, Ross wrote:
> > On 27 September 2017 at 18:00, Tom Rini <trini@konsulko.com> 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.
> >
> > Doesn't bmap in Pyro use Python 2?
>
> I hadn't tested my fix in pyro yet, only confirmed that it was broken
> there. I'll check and get back to you on that part.
OK, I need to investigate the pyro failure I saw more to see what else
was going in there. Just oe-core pyro is fine as bamptool uses python2
and .../recipe-sysroot-native/usr/bin/bmaptool is /usr/bin/env
nativepython which is also in usr/bin and is thus found.
--
Tom
next prev parent reply other threads:[~2017-09-27 19:34 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 [this message]
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
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=20170927193441.GA3112@bill-the-cat \
--to=trini@konsulko.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox