From: Lianhao Lu <lianhao.lu@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH V2 0/1] multilib header support for python
Date: Fri, 6 Apr 2012 10:40:01 +0800 [thread overview]
Message-ID: <cover.1333679903.git.lianhao.lu@intel.com> (raw)
Added multilib header support for python, so that lib32-python and python won't have
conflicting file pyconfig.h.
The following changes since commit 1a82989345fb98becb487d270fd93a5e6dffeb47:
Saul Wold (1):
runqemu-internal: Add console=tty for qemuppc and NFS
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib llu/multilib2
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=llu/multilib2
Lianhao Lu (1):
python: multilib header support.
.../python/python-2.7-manifest.inc | 2 +-
meta/recipes-devtools/python/python.inc | 2 +-
meta/recipes-devtools/python/python_2.7.2.bb | 4 +++-
scripts/contrib/python/generate-manifest-2.7.py | 2 +-
4 files changed, 6 insertions(+), 4 deletions(-)
next reply other threads:[~2012-04-06 2:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-06 2:40 Lianhao Lu [this message]
2012-04-06 2:40 ` [PATCH V2 1/1] python: multilib header support Lianhao Lu
2012-04-11 15:26 ` [PATCH V2 0/1] multilib header support for python Saul Wold
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.1333679903.git.lianhao.lu@intel.com \
--to=lianhao.lu@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