From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
"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 15:31:12 +0000 [thread overview]
Message-ID: <47f71734c82e4cf48fa59d3f544c97b0@axis.com> (raw)
In-Reply-To: <af998e903fb8c67e2c19adcc59225b84e1f92384.camel@linuxfoundation.org>
> -----Original Message-----
> From: Richard Purdie <richard.purdie@linuxfoundation.org>
> Sent: den 14 mars 2022 14:45
> To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>; OE Core
> (openembedded-core@lists.openembedded.org) <openembedded-
> core@lists.openembedded.org>
> Subject: Re: [OE-core] Building python3 without readline fails for
> Kirkstone
>
> On Mon, 2022-03-14 at 13:39 +0000, Peter Kjellerstedt 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.
> >
> > Any help to solve the problem would be appreciated.
>
> I'd have thought that those modules being missing was probably expected if
> you disable readline?
AFAICT, both curses and curses_panel are built for Hardknott and
Honister even if readline is removed from PACKAGECONFIG.
> Cheers,
>
> Richard
//Peter
next prev parent reply other threads:[~2022-03-14 15:31 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 [this message]
2022-03-14 16:01 ` Ross Burton
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=47f71734c82e4cf48fa59d3f544c97b0@axis.com \
--to=peter.kjellerstedt@axis.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox