All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Oleksandr Kravchuk <open.source@oleksandr-kravchuk.com>,
	OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/6] python-scons: update to 3.1.0
Date: Tue, 23 Jul 2019 11:35:12 +0300	[thread overview]
Message-ID: <20190723083512.GC27144@localhost> (raw)
In-Reply-To: <CAJTo0LZDXcLhYqvgYmY4-hX4Uc+ZJniDhqWkrjtaYu_k58Fr8w@mail.gmail.com>

On Tue, Jul 23, 2019 at 08:47:16AM +0100, Burton, Ross wrote:
> On Tue, 23 Jul 2019 at 06:43, Adrian Bunk <bunk@stusta.de> wrote:
> > On Mon, Jul 22, 2019 at 10:51:35AM +0100, Burton, Ross wrote:
> > > Do we need the Python 2 variation of scons in oe-core, or even at all?
> >
> > Regarding the latter, do you see what is needed for making gpsd in
> > meta-oe working with the Python 3 variant?
> >
> > Upstream seems to support it, but it fails to build.
> >
> > I thought I knew what the problem was, but it turned out to be wrong.
> 
> So that's a 'yes', fair enough.  Is gpsd the only piece that needs it?

In meta-openembedded the only other recipe using scons is
PNBLACKLIST[mongodb] = "Since bbclass scons convert to python3, build mongodb failed"

So 2/2 of the scons-using recipes in meta-openembedded so not work with 
the Python 3 version right now, and there might be more in other layers.

> Ross

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed



  reply	other threads:[~2019-07-23  8:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-22  0:18 [PATCH 1/6] python-scons: update to 3.1.0 Oleksandr Kravchuk
2019-07-22  0:18 ` [PATCH 2/6] python3-scons: " Oleksandr Kravchuk
2019-07-22  0:18 ` [PATCH 3/6] python3-docutils: update to 0.15 Oleksandr Kravchuk
2019-07-22  0:18 ` [PATCH 4/6] python3-git: update to 2.1.12 Oleksandr Kravchuk
2019-07-22 10:15   ` Burton, Ross
2019-07-22 10:16     ` Burton, Ross
2019-07-22 15:53       ` Oleksandr Kravchuk
2019-07-22 16:03         ` Burton, Ross
2019-07-22  0:18 ` [PATCH 5/6] python3-mako: update to 1.0.14 Oleksandr Kravchuk
2019-07-22  0:18 ` [PATCH 6/6] python3-pbr: update to 5.4.1 Oleksandr Kravchuk
2019-07-22  9:51 ` [PATCH 1/6] python-scons: update to 3.1.0 Burton, Ross
2019-07-23  5:43   ` Adrian Bunk
2019-07-23  7:47     ` Burton, Ross
2019-07-23  8:35       ` Adrian Bunk [this message]
2019-07-23  9:03         ` Burton, Ross
2019-07-23 16:51           ` Adrian Bunk

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=20190723083512.GC27144@localhost \
    --to=bunk@stusta.de \
    --cc=open.source@oleksandr-kravchuk.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.