From: Yu Ke <ke.yu@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 00/10] [RFC] patch for non /usr/lib libdir - V2
Date: Mon, 11 Jul 2011 15:23:13 +0800 [thread overview]
Message-ID: <cover.1310368636.git.ke.yu@intel.com> (raw)
This is the V2 patches. the changes compared to V1 are:
- revise python patch to make the sys.lib deriving from libdir, instead of hardcode to lib64
- add two more fixes: sat-solver and libzypp, with these two more fixes, i can build
qemux86-64 core-image-sato and core-image-sato-sdk with libdir=/usr/lib64
Next step, I will do through test to make sure it does not impact normal libdir=/usr/lib case
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-v2
http://git.pokylinux.org/cgit.cgi//log/?h=kyu3/libdir-fix-v2
Yu Ke (10):
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
sat-solver: fix for non /usr/lib libdir case
libzypp: fix for non /usr/lib libdir case
meta/classes/cmake.bbclass | 4 +
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 | 250 ++++++++++++++++++++
meta/recipes-devtools/python/python_2.6.6.bb | 3 +-
meta/recipes-devtools/rpm/rpm_5.4.0.bb | 3 +-
.../libzypp/libzypp/hardcode-lib-fix.patch | 22 ++
meta/recipes-extended/libzypp/libzypp_git.bb | 5 +-
meta/recipes-extended/sat-solver/sat-solver_git.bb | 6 +-
meta/recipes-support/libcap/libcap.inc | 5 +-
meta/recipes-support/libcap/libcap_2.20.bb | 2 +-
16 files changed, 311 insertions(+), 19 deletions(-)
create mode 100644 meta/recipes-devtools/python/python/multilib.patch
create mode 100644 meta/recipes-extended/libzypp/libzypp/hardcode-lib-fix.patch
next reply other threads:[~2011-07-11 7:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-11 7:23 Yu Ke [this message]
2011-07-11 7:23 ` [PATCH 01/10] native.bbclass: generate libdir from libdir_native Yu Ke
2011-07-11 7:23 ` [PATCH 02/10] openssl: fix for non /usr/lib libdir case Yu Ke
2011-07-11 7:23 ` [PATCH 03/10] libc-package.bbclass: " Yu Ke
2011-07-11 7:23 ` [PATCH 04/10] python: fix for libdir=/usr/lib64 case Yu Ke
2011-07-11 7:23 ` [PATCH 05/10] python-native: fix for non /usr/lib libdir case Yu Ke
2011-07-11 7:23 ` [PATCH 06/10] perl: " Yu Ke
2011-07-11 7:23 ` [PATCH 07/10] libcap: " Yu Ke
2011-07-11 7:23 ` [PATCH 08/10] rpm: " Yu Ke
2011-07-11 7:23 ` [PATCH 09/10] sat-solver: " Yu Ke
2011-07-11 7:40 ` [PATCH 00/10] [RFC] patch for non /usr/lib libdir - V2 Koen Kooi
2011-07-11 7:54 ` Yu Ke
2011-07-11 8:13 ` Koen Kooi
2011-07-12 13:59 ` 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.1310368636.git.ke.yu@intel.com \
--to=ke.yu@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 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.