Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Dongxiao Xu <dongxiao.xu@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/6][PULL v2] multilib: bug fixes related with RPM backend
Date: Wed, 28 Sep 2011 19:44:25 +0800	[thread overview]
Message-ID: <cover.1317209357.git.dongxiao.xu@intel.com> (raw)

Hi Richard,

This pull request is to fix several multilib bugs related with RPM backend,
please help to review and pull.

Changes from v1:
 - Add a patch to handle PACKAGES dynamic setting in libc-package.bbclass in
multilib case. Otherwise IPK packaging logic will not find the correct
locale-base-* packages.

I've done a round of multilib testing agasint for following combinations for
both RPM and IPK packaging:

 - lib32 sato image on qemux86 machine
 - lib32 sato image on qemux86-64 machine
 - lib64 sato image on qemux86-64 machine
 - lib64 sato image on qemux86 machine (build pass but cannot boot)
 - sato image on qemux86-64 with several lib32 packages (lib32-connman)

All the above test cases can pass the build and most can successfully boot up
(except the lib64 on qemux86 since 64bit code could not run on 32bit machine).

Therefore the following bugs could be addressed:

[YOCTO #1496]
[YOCTO #1497]
[YOCTO #1498]
[YOCTO #1527]

Thanks,
Dongxiao

The following changes since commit 684a4b517d13884c315688967fadd5e6a4845b71:

  libffi: really populate -dev package (2011-09-26 20:50:27 +0100)

are available in the git repository at:
  git://git.pokylinux.org/poky-contrib dxu4/ml
  http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=dxu4/ml

Dongxiao Xu (6):
  multilib.bbclass: map RDEPENDS and LINGUAS_INSTALL for image recipes
  multilib: remove the multilib handling to allarch
  multilib: add MLPREFIX to deploy folder
  tune-i586: fix hardcoded TUNE_PKGARCH
  package_rpm: combine normal and multilib solution manifest together
  libc-package.bbclass: add MLPREFIX when set values to PACKAGES

 meta/classes/libc-package.bbclass                  |    2 +-
 meta/classes/multilib.bbclass                      |   12 +++++-------
 meta/classes/multilib_global.bbclass               |    2 +-
 meta/classes/package_rpm.bbclass                   |   15 +++++++++++----
 meta/classes/rootfs_rpm.bbclass                    |    2 +-
 meta/conf/machine/include/tune-i586.inc            |    3 ++-
 meta/conf/multilib.conf                            |    7 +++++++
 .../python/python-pygobject_2.27.91.bb             |    2 +-
 8 files changed, 29 insertions(+), 16 deletions(-)




             reply	other threads:[~2011-09-28 11:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-28 11:44 Dongxiao Xu [this message]
2011-09-28 11:44 ` [PATCH 1/6] multilib.bbclass: map RDEPENDS and LINGUAS_INSTALL for image recipes Dongxiao Xu
2011-09-28 11:44 ` [PATCH 2/6] multilib: remove the multilib handling to allarch Dongxiao Xu
2011-09-28 11:44 ` [PATCH 3/6] multilib: add MLPREFIX to deploy folder Dongxiao Xu
2011-09-28 11:44 ` [PATCH 4/6] tune-i586: fix hardcoded TUNE_PKGARCH Dongxiao Xu
2011-09-28 11:44 ` [PATCH 5/6] package_rpm: combine normal and multilib solution manifest together Dongxiao Xu
2011-09-28 11:44 ` [PATCH 6/6] libc-package.bbclass: add MLPREFIX when set values to PACKAGES Dongxiao Xu

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.1317209357.git.dongxiao.xu@intel.com \
    --to=dongxiao.xu@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