All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ross Burton <ross@burtonini.com>
To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>,
	Alexander Kanavin <alex.kanavin@gmail.com>
Cc: "OE Core (openembedded-core@lists.openembedded.org)"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] Building python3 without readline fails for Kirkstone
Date: Mon, 14 Mar 2022 16:01:51 +0000	[thread overview]
Message-ID: <CAAnfSTuXkAQyGW_KoQYMJQHM=hFte_wU6rKuAcof2bddUHAB6Q@mail.gmail.com> (raw)
In-Reply-To: <1fcdfa7197764e3ebeeb5ace0b99a550@axis.com>

On Mon, 14 Mar 2022 at 13:39, Peter Kjellerstedt
<peter.kjellerstedt@axis.com> wrote:
>
> We have readline support disabled for python3 for target. It works
> fine for Hardknott and Honister, but fails for Kirkstone with the
> following error:
>
>   The necessary bits to build these optional modules were not found:
>   _curses               _curses_panel
>
> The problem can be recreated by adding the following to local.conf:
>
> PACKAGECONFIG:remove:pn-python3:class-target = "readline"
>
> and then building python3.

The sanity check code has support for modules which have been disabled
(see MODDISABLED_NAMES in
meta/recipes-devtools/python/python3/0017-setup.py-do-not-report-missing-dependencies-for-disa.patch)
but that variable doesn't appear to be connected to the PACKAGECONFIG
settings.

Adding AlexK to the CC list as he wrote this in the first place.

Ross


  parent reply	other threads:[~2022-03-14 16:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-14 13:39 Building python3 without readline fails for Kirkstone Peter Kjellerstedt
2022-03-14 13:45 ` [OE-core] " Richard Purdie
2022-03-14 15:31   ` Peter Kjellerstedt
2022-03-14 16:01 ` Ross Burton [this message]
2022-03-14 16:20   ` Alexander Kanavin

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='CAAnfSTuXkAQyGW_KoQYMJQHM=hFte_wU6rKuAcof2bddUHAB6Q@mail.gmail.com' \
    --to=ross@burtonini.com \
    --cc=alex.kanavin@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=peter.kjellerstedt@axis.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.