From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>,
Andrew Geissler <geissonator@gmail.com>,
Christopher Larson <chris_larson@mentor.com>
Cc: yocto@lists.yoctoproject.org
Subject: Re: [yocto] devtool modify issues with ubuntu 20 and fedora core 32
Date: Wed, 03 Jun 2020 14:42:57 +0100 [thread overview]
Message-ID: <115f3f1f445a163af79f94cdd48b497f478ae85d.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj_39Vq-1754skg3Zhvkt+jU1bDwKVDVar0jZovZC4P3WQ@mail.gmail.com>
On Wed, 2020-06-03 at 11:06 +0200, Alexander Kanavin wrote:
> I'm not sure if this is distro specific. _PYTHON_SYSCONFIGDATA_NAME
> is set from python3native.bbclass so that native python can pick up
> target configuration, and if the target configuration is not there
> (it comes with target python3 build), then there will be a failure
> like the above. How does your recipe look like? Do you get the same
> failure if you try devtool modify in a plain yocto environment (not
> the SDK)?
Chris and I did talk about this on irc:
(22:33:38) kergoth: actually fails even without prserv enabled at all
(22:34:07) kergoth: just import pydoc will call sysconfig.get_path() which enters that codepath
(22:34:22) kergoth: so calling anything that imports bb from a task will explode
(22:34:33) kergoth: cooker pulls in xmlrpc, which pulls in pydoc
(22:34:41) kergoth: breaks devtool modify
(22:37:04) RP: kergoth: right, it was more about it being a hint at the kinds of issues
(22:37:11) kergoth: ah, fair enough
(22:37:26) kergoth: i expect we may need to change how python3native is doing its thing
(22:42:55) RP: kergoth: quite possibly. I never liked that fix and suspected there was more to it :/
(23:21:39) kergoth: RP: maybe something like https://github.com/openembedded/openembedded-core/compare/master...kergoth:python-sysconfig ? i'll mull it over. makes sense, though. we rename _sysconfig only for the python3-native recipe, so it'd make sense for us to only change that name for our python, not any python run from the task
(23:21:49) kergoth: _sysconfigdata, that is
(23:46:35) RP: kergoth: something like that would make sense, yes
Chris: Did you come to any conclusion?
Does someone want to send a patch?
Cheers,
Richard
next prev parent reply other threads:[~2020-06-03 13:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 21:28 devtool modify issues with ubuntu 20 and fedora core 32 Andrew Geissler
2020-06-03 9:06 ` [yocto] " Alexander Kanavin
2020-06-03 13:42 ` Richard Purdie [this message]
2020-06-03 14:40 ` kergoth
2020-06-14 23:31 ` Peter Kjellerstedt
2020-10-27 10:14 ` ernst.sjostrand
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=115f3f1f445a163af79f94cdd48b497f478ae85d.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alex.kanavin@gmail.com \
--cc=chris_larson@mentor.com \
--cc=geissonator@gmail.com \
--cc=yocto@lists.yoctoproject.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