All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: richard.purdie@linuxfoundation.org
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: new meta-oe failures from master-next
Date: Thu, 24 Oct 2019 12:34:06 +0300	[thread overview]
Message-ID: <20191024093406.GA27204@localhost> (raw)
In-Reply-To: <25022a4c11222cda48ad70ae0f7bce0625678f15.camel@linuxfoundation.org>

On Thu, Oct 24, 2019 at 09:15:01AM +0100, richard.purdie@linuxfoundation.org wrote:
> 
> The cmake change makes python visible from HOSTTOOLS. That isn't wrong
> as such, it is a change in behaviour. If recipes don't set python
> enabled/disabled explicitly, there is some fallout from that. I'd say
> that is a bug in those recipes which aren't giving explicit
> configuration to dependencies though.

The problem is not about enable/disable, it is more about not explicitly 
selecting the python version.

For the affected libiio the python2 -> python3 change of the python 
bindings last week [1] was basically:

-inherit cmake pythonnative systemd
+inherit cmake python3native systemd

This is very fragile, and I would consider it expected that either the 
old or the new case will break in some way when both python2 and python3
are available during the build.

> Cheers,
> 
> RIchard

cu
Adrian

[1] http://git.openembedded.org/meta-openembedded/commit/?id=6af155513506f6a0a3a44b66fb48897f22fb2c2f

-- 

       "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



  parent reply	other threads:[~2019-10-24  9:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-23 13:03 new meta-oe failures from master-next Khem Raj
2019-10-23 13:05 ` Khem Raj
2019-10-23 15:58   ` akuster808
2019-10-23 15:29 ` Ross Burton
2019-10-23 19:23   ` Adrian Bunk
2019-10-23 21:20     ` Richard Purdie
2019-10-23 22:08       ` Adrian Bunk
2019-10-23 19:31   ` Richard Purdie
2019-10-23 22:52     ` Khem Raj
2019-10-24  6:37       ` Khem Raj
2019-10-24  8:15       ` richard.purdie
2019-10-24  8:20         ` Khem Raj
2019-10-24  8:25           ` richard.purdie
2019-10-24  8:34             ` Khem Raj
2019-10-24  9:34               ` richard.purdie
2019-10-24  9:34         ` Adrian Bunk [this message]
2019-10-24  9:43           ` richard.purdie
2019-10-23 16:22 ` richard.purdie

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=20191024093406.GA27204@localhost \
    --to=bunk@stusta.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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 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.