From: Yu Ke <ke.yu@intel.com>
To: openembedded-core@lists.openembedded.org,
richard.purdie@linuxfoundation.org
Subject: [PATCH 0/8] [RFC] patch for non /usr/lib libdir
Date: Thu, 7 Jul 2011 22:10:04 +0800 [thread overview]
Message-ID: <cover.1310047266.git.ke.yu@intel.com> (raw)
in multilib case, libdir is usually not standard /usr/lib, so this series of
patches are addressing some recipes's build failure when libdir is not /usr/lib,
for example, libdir=/usr/lib64.
All the patches have no impact to current libdir=/usr/lib situation, since
they just replace the hardcode /usr/lib with libdir.
Signed-off-by: Yu Ke <ke.yu@intel.com>
The following changes since commit 2163461ec94528ecf046a04edc5db3d2dd3a6b8b:
Tom Zanussi (1):
systemtap: remove non-core COMPATIBLE_MACHINES
are available in the git repository at:
git://git.pokylinux.org/poky-contrib kyu3/libdir-fix
http://git.pokylinux.org/cgit.cgi//log/?h=kyu3/libdir
Yu Ke (8):
native.bbclass: generate libdir from libdir_native
openssl: fix for non /usr/lib libdir case
libc-package.bbclass: fix for non /usr/lib libdir case
python: fix for libdir=/usr/lib64 case
python-native: fix for non /usr/lib libdir case
perl: fix for non /usr/lib libdir case
libcap: fix for non /usr/lib libdir case
rpm: fix for non /usr/lib libdir case
meta/classes/libc-package.bbclass | 4 +-
meta/classes/native.bbclass | 2 +
meta/recipes-connectivity/openssl/openssl.inc | 2 +-
.../recipes-connectivity/openssl/openssl_0.9.8r.bb | 2 +-
meta/recipes-devtools/perl/perl_5.12.3.bb | 3 +-
...2-distutils-prefix-is-inside-staging-area.patch | 15 +-
.../recipes-devtools/python/python-native_2.6.6.bb | 2 +-
meta/recipes-devtools/python/python/multilib.patch | 295 ++++++++++++++++++++
meta/recipes-devtools/python/python_2.6.6.bb | 3 +-
meta/recipes-devtools/rpm/rpm_5.4.0.bb | 3 +-
meta/recipes-support/libcap/libcap.inc | 5 +-
meta/recipes-support/libcap/libcap_2.20.bb | 2 +-
12 files changed, 323 insertions(+), 15 deletions(-)
create mode 100644 meta/recipes-devtools/python/python/multilib.patch
next reply other threads:[~2011-07-07 14:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-07 14:10 Yu Ke [this message]
2011-07-07 14:10 ` [PATCH 1/8] native.bbclass: generate libdir from libdir_native Yu Ke
2011-07-07 14:10 ` [PATCH 2/8] openssl: fix for non /usr/lib libdir case Yu Ke
2011-07-07 14:10 ` [PATCH 3/8] libc-package.bbclass: " Yu Ke
2011-07-08 17:15 ` Richard Purdie
2011-07-07 14:10 ` [PATCH 4/8] python: fix for libdir=/usr/lib64 case Yu Ke
2011-07-07 19:22 ` Richard Purdie
2011-07-08 0:52 ` Yu Ke
2011-07-07 14:10 ` [PATCH 5/8] python-native: fix for non /usr/lib libdir case Yu Ke
2011-07-07 14:10 ` [PATCH 6/8] perl: " Yu Ke
2011-07-07 16:14 ` Kamble, Nitin A
2011-07-07 19:21 ` Richard Purdie
2011-07-07 14:10 ` [PATCH 7/8] libcap: " Yu Ke
2011-07-07 14:10 ` [PATCH 8/8] rpm: " Yu Ke
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.1310047266.git.ke.yu@intel.com \
--to=ke.yu@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.