From: Markus Lehtonen <markus.lehtonen@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH v9 00/14] support profile-optimized build for Python
Date: Thu, 11 Jan 2018 13:47:17 +0200 [thread overview]
Message-ID: <cover.1515670916.git.markus.lehtonen@linux.intel.com> (raw)
Changes since v8:
- rebased onto latest master
- fixed a logger naming mistake in python-pgo-image.bb - this mistake caused
the targetrunner logs not to be printed at all
The following changes since commit e9dfe7eb7f61b909ae7d034e80cfbebc1fad018b:
icu-dbg: improve reproducibility (2018-01-08 08:45:33 +0000)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib marquiz/fixes-9338
http://cgit.openembedded.org/openembedded-core-contrib/log/?h=marquiz/fixes-9338
Markus Lehtonen (14):
python3-native: support profile optimized build
python3: fix depends of python3-tests
python3: add python3-profile-opt recipe
python3-profile-opt: rename libpython3
openssh: extend to -native
iptables: enable native
iproute2: enable native
oeqa/targetcontrol: re-introduce get_target_controller()
oeqa/targetcontrol: add missing arg to SimpleRemoteTarget.__init__
devtools/images: add python-pgo-image
python3: support profile optimized build
python3: fix profile-optimized build of modules
python3: add python3-tools subpackage
oeqa: add selftest for python pgo
meta/lib/oeqa/selftest/cases/python.py | 28 ++++++
meta/lib/oeqa/targetcontrol.py | 29 +++++-
meta/recipes-connectivity/iproute2/iproute2.inc | 7 +-
...1-don-t-use-absolute-path-for-ssh-program.patch | 31 ++++++
meta/recipes-connectivity/openssh/openssh_7.6p1.bb | 8 +-
meta/recipes-devtools/images/python-pgo-image.bb | 92 ++++++++++++++++++
.../python/python-3.5-manifest.inc | 13 ++-
.../python/python3-native_3.5.3.bb | 9 ++
meta/recipes-devtools/python/python3-profile-opt | 1 +
.../python/python3-profile-opt_3.5.3.bb | 10 ++
.../python3/0001-cross-compile-support.patch | 9 --
...efile-add-install_generate_profile-target.patch | 25 +++++
...-CFLAGS-for-extensions-when-cross-compili.patch | 56 +++++++++++
...name-libpython3-to-libpython-profile-opt3.patch | 108 +++++++++++++++++++++
meta/recipes-devtools/python/python3_3.5.3.bb | 56 ++++++++---
...revent-absolute-path-in-installed-symlink.patch | 29 ++++++
meta/recipes-extended/iptables/iptables_1.6.1.bb | 3 +
scripts/contrib/python/generate-manifest-3.5.py | 5 +-
18 files changed, 489 insertions(+), 30 deletions(-)
create mode 100644 meta/lib/oeqa/selftest/cases/python.py
create mode 100644 meta/recipes-connectivity/openssh/openssh/0001-don-t-use-absolute-path-for-ssh-program.patch
create mode 100644 meta/recipes-devtools/images/python-pgo-image.bb
create mode 120000 meta/recipes-devtools/python/python3-profile-opt
create mode 100644 meta/recipes-devtools/python/python3-profile-opt_3.5.3.bb
create mode 100644 meta/recipes-devtools/python/python3/Makefile-add-install_generate_profile-target.patch
create mode 100644 meta/recipes-devtools/python/python3/Use-correct-CFLAGS-for-extensions-when-cross-compili.patch
create mode 100644 meta/recipes-devtools/python/python3/rename-libpython3-to-libpython-profile-opt3.patch
create mode 100644 meta/recipes-extended/iptables/iptables/prevent-absolute-path-in-installed-symlink.patch
--
2.13.6
reply other threads:[~2018-01-11 11:47 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=cover.1515670916.git.markus.lehtonen@linux.intel.com \
--to=markus.lehtonen@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