Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Dongxiao Xu <dongxiao.xu@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1][PULL] fix /bin/sh missing in multilib case
Date: Fri,  5 Aug 2011 13:48:24 +0800	[thread overview]
Message-ID: <cover.1312522526.git.dongxiao.xu@intel.com> (raw)

Hi Richard,

This pull request fixes the /bin/sh missing issue in doing multilib rootfs of
lib32-core-image-sato.

multilib.bbclass will check whether PACKAGES are begin with MLPREFIX. If not,
it will tries to rename variables like: FILES_pkg, RDEPENDS_pkg, etc.

Recipe task-core-boot RDEPENDS some key recipes like busybox, tinylogin, etc,
while it doesn't have PACKAGES defined, so it will use default PACKAGES
definition in bitbake:

"${PN}-dbg ${PN} ${PN}-doc ${PN}-dev ${PN}-staticdev ${PN}-locale".

${PN} is begin with MLPREFIX, therefore for PACKAGES of task-core-boot, no
rename occurred, resulting that RDEPENDS_lib32-task-core-boot is empty.
busybox, tinylogin, etc. are not built out, which caused the missing of /bin/sh.

Like the other task-core-xxx.bb files, this commit explicitly defines PACKAGES
in task-core-boot.bb to fix this issue.

Thanks,
Dongxiao

The following changes since commit 8a731122e7811275f20065ba27645b97fadf362d:

  eglibc: Fix patch merge breakage (2011-08-04 15:41:08 +0100)

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

Dongxiao Xu (1):
  task-core-boot.bb: Add PACKAGE definition to facilitate multilib

 meta/recipes-core/tasks/task-core-boot.bb |    8 +++++++-
 1 files changed, 7 insertions(+), 1 deletions(-)




             reply	other threads:[~2011-08-05  5:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-05  5:48 Dongxiao Xu [this message]
2011-08-05  5:48 ` [PATCH 1/1] task-core-boot.bb: Add PACKAGE definition to facilitate multilib Dongxiao Xu
2011-08-05 16:28   ` Richard Purdie

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.1312522526.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