From: <jackie.huang@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Cc: qingtao.cao@windriver.com, Jackie.Huang@windriver.com
Subject: [PATCH 0/4] Multilib: fix PN -> BPN in do_install for some recipes
Date: Fri, 15 Mar 2013 16:03:59 +0800 [thread overview]
Message-ID: <cover.1363333753.git.jackie.huang@windriver.com> (raw)
From: Jackie Huang <jackie.huang@windriver.com>
tested with:
MULTILIBS ?= "multilib:lib32"
DEFAULTTUNE_virtclass-multilib-lib32 ?= "x86"
$ bitbake python-imaging lib32-python-imaging \
liberation-fonts lib32-liberation-fonts \
ttf-bitstream-vera lib32-ttf-bitstream-vera \
gnupg lib32-gnupg libatomics-ops lib32-libatomics-ops
The following changes since commit f46cf86d0ec3b80ce526b4dad1b1eac5995969ec:
icecc: improve interaction with sstate (2013-03-15 01:52:54 +0000)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib jhuang0/d_bpn_0315_1
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=jhuang0/d_bpn_0315_1
Jackie Huang (4):
python-imaging: fix PN -> BPN in do_install for multilibs
gnupg: fix PN -> BPN in do_install for multilibs
ttf-fonts: fix PN -> BPN in do_install for multilibs
libatomics-ops: fix PN -> BPN in do_install for multilibs
.../python/python-imaging_1.1.7.bb | 8 ++++----
.../ttf-fonts/liberation-fonts_1.04.bb | 6 +++---
.../ttf-fonts/liberation-fonts_1.06.bb | 6 +++---
.../ttf-fonts/ttf-bitstream-vera_1.10.bb | 6 +++---
.../pulseaudio/libatomics-ops_7.2.bb | 4 ++--
meta/recipes-support/gnupg/gnupg_1.4.7.bb | 12 ++++++------
6 files changed, 21 insertions(+), 21 deletions(-)
--
1.7.4.1
next reply other threads:[~2013-03-15 11:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 8:03 jackie.huang [this message]
2013-03-15 8:04 ` [PATCH 1/4] python-imaging: fix PN -> BPN in do_install for multilibs jackie.huang
2013-03-15 8:04 ` [PATCH 2/4] gnupg: " jackie.huang
2013-03-15 8:04 ` [PATCH 3/4] ttf-fonts: " jackie.huang
2013-03-15 8:04 ` [PATCH 4/4] libatomics-ops: " jackie.huang
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.1363333753.git.jackie.huang@windriver.com \
--to=jackie.huang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=qingtao.cao@windriver.com \
/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