From: Kai Kang <kai.kang@windriver.com>
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH V4 0/6] allarch: disable allarch when multilib is used
Date: Sun, 26 Aug 2018 06:06:25 -0700 [thread overview]
Message-ID: <cover.1535288685.git.kai.kang@windriver.com> (raw)
V4:
* rebase on origin/master-next
* update postinstall script update_gtk_immodules_cache
V3:
* drop commit "cmake.bbclass: fix wrong toolchain flags of nativesdk package"
which causes some oe-selftest cases fail
* update postinstall script update_font_cache
* drop oe-selftest case test_sstate_allarch_samesigs_multilib
* fix some install file conflicts
The following changes since commit ec8f8ba112abe2d57b91a00d0c9d6c9a597f83a0:
cmake: add CMAKE_SYSROOT to generated toolchain file (2018-08-24 16:01:59 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib kangkai/allarch-enabled-V4
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=kangkai/allarch-enabled-V4
Kai Kang (6):
allarch: disable allarch when multilib is used
sstate.bbclass: update SSTATE_DUPWHITELIST
update_font_cache: update script for multilib
update_gtk_immodules_cache: update for multilib
statetests.py: drop test_sstate_allarch_samesigs_multilib
multilib: fix install file conflicts
meta/classes/allarch-enabled.bbclass | 52 ++++++++++++++++++++++
meta/classes/allarch.bbclass | 51 +--------------------
meta/classes/icecc.bbclass | 2 +-
meta/classes/multilib.bbclass | 2 +-
meta/classes/multilib_global.bbclass | 2 +-
meta/classes/package.bbclass | 6 +--
meta/classes/sstate.bbclass | 4 +-
meta/lib/oeqa/selftest/cases/sstatetests.py | 11 +----
meta/recipes-core/udev/eudev_3.2.5.bb | 6 ++-
.../gobject-introspection_1.56.1.bb | 6 ++-
meta/recipes-gnome/gtk+/gtk+.inc | 4 ++
meta/recipes-gnome/gtk+/gtk+3.inc | 4 ++
meta/recipes-graphics/cairo/cairo_1.14.12.bb | 6 ++-
.../fontconfig/fontconfig_2.12.6.bb | 8 +++-
meta/recipes-support/icu/icu.inc | 4 +-
.../libgpg-error/libgpg-error_1.32.bb | 5 ++-
scripts/postinst-intercepts/update_font_cache | 2 +-
.../postinst-intercepts/update_gtk_immodules_cache | 8 ++--
18 files changed, 104 insertions(+), 79 deletions(-)
create mode 100644 meta/classes/allarch-enabled.bbclass
--
2.11.0
next reply other threads:[~2018-08-26 13:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-26 13:06 Kai Kang [this message]
2018-08-26 13:06 ` [PATCH 1/6] allarch: disable allarch when multilib is used Kai Kang
2018-09-04 8:36 ` richard.purdie
2018-09-04 9:07 ` Kang Kai
2018-09-05 2:52 ` Kang Kai
2018-09-05 21:34 ` richard.purdie
2018-08-26 13:06 ` [PATCH 2/6] sstate.bbclass: update SSTATE_DUPWHITELIST Kai Kang
2018-08-26 13:06 ` [PATCH 3/6] update_font_cache: update script for multilib Kai Kang
2018-09-04 9:12 ` richard.purdie
2018-09-04 9:41 ` Kang Kai
2018-08-26 13:06 ` [PATCH 4/6] update_gtk_immodules_cache: update " Kai Kang
2018-08-26 13:06 ` [PATCH 5/6] statetests.py: drop test_sstate_allarch_samesigs_multilib Kai Kang
2018-08-26 13:06 ` [PATCH 6/6] multilib: fix install file conflicts Kai Kang
2018-09-04 9:16 ` richard.purdie
2018-09-04 9:52 ` Kang Kai
2018-08-26 13:33 ` ✗ patchtest: failure for allarch: disable allarch when multilib is used (rev4) Patchwork
2018-08-26 13:58 ` Kang Kai
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.1535288685.git.kai.kang@windriver.com \
--to=kai.kang@windriver.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