From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH] python3-native: fix build races in 'make regen-all'
Date: Thu, 15 Mar 2018 18:54:58 +0200 [thread overview]
Message-ID: <20180315165458.42134-1-alexander.kanavin@linux.intel.com> (raw)
Python 2.x and target Python 3.x do not have this issue.
[YOCTO #12596]
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
---
meta/recipes-devtools/python/python3-native_3.5.4.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/recipes-devtools/python/python3-native_3.5.4.bb b/meta/recipes-devtools/python/python3-native_3.5.4.bb
index c8252539a99..a5dedb7aa75 100644
--- a/meta/recipes-devtools/python/python3-native_3.5.4.bb
+++ b/meta/recipes-devtools/python/python3-native_3.5.4.bb
@@ -64,6 +64,8 @@ do_configure_append() {
# Regenerate all of the generated files
# This ensures that pgen and friends get created during the compile phase
do_compile_prepend() {
+ # Has to be done ahead of other regen- targets due to https://bugs.python.org/issue33080
+ oe_runmake regen-importlib
oe_runmake regen-all
}
--
2.16.1
reply other threads:[~2018-03-15 17:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180315165458.42134-1-alexander.kanavin@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.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