From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/3] Fixes for python-native and runqemu with uclibc
Date: Tue, 29 Nov 2011 07:49:11 -0800 [thread overview]
Message-ID: <4ED4FEF7.4020800@linux.intel.com> (raw)
In-Reply-To: <cover.1322444142.git.raj.khem@gmail.com>
On 11/27/2011 05:46 PM, Khem Raj wrote:
> These patches fix a problem with python-native
> and other patches to get runqemu working with uclibc
>
> The following changes since commit a14b41f4de3ea6c3f00ff7a1d0441483e40b28de:
>
> default-distrovars: Define SDK_VERSION and DISTRO_VERSION (2011-11-27 17:32:00 -0800)
>
> are available in the git repository at:
> git://git.openembedded.org/openembedded-core-contrib kraj/misc
> http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=kraj/misc
>
> Khem Raj (3):
> default-distrovars: Define SDK_VERSION and DISTRO_VERSION
> toolchain-scripts.bbclass: Make it work when TCLIBC=uclibc
> python-native: Fix gcc compiler detecting logic
>
> meta/classes/toolchain-scripts.bbclass | 8 +++++-
> meta/conf/distro/include/default-distrovars.inc | 3 +-
> .../python/python-native/unixccompiler.patch | 22 ++++++++++----------
> .../recipes-devtools/python/python-native_2.7.2.bb | 2 +-
> 4 files changed, 20 insertions(+), 15 deletions(-)
>
Merged into OE-Core
Thanks
Sau!
prev parent reply other threads:[~2011-11-29 15:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-28 1:45 [PATCH 0/3] Fixes for python-native and runqemu with uclibc Khem Raj
2011-11-28 1:46 ` [PATCH 1/3] default-distrovars: Define SDK_VERSION and DISTRO_VERSION Khem Raj
2011-11-28 1:46 ` [PATCH 2/3] toolchain-scripts.bbclass: Make it work when TCLIBC=uclibc Khem Raj
2011-11-28 1:46 ` [PATCH 3/3] python-native: Fix gcc compiler detecting logic Khem Raj
2011-11-29 15:49 ` Saul Wold [this message]
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=4ED4FEF7.4020800@linux.intel.com \
--to=sgw@linux.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