From: nitin.a.kamble@intel.com
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/4] x32 recipe fixes + misc commits
Date: Wed, 4 Jan 2012 17:02:08 -0800 [thread overview]
Message-ID: <cover.1325725256.git.nitin.a.kamble@intel.com> (raw)
From: Nitin A Kamble <nitin.a.kamble@intel.com>
The following changes since commit 021848be9eeb71de8acfba6c66c11645b01523b8:
valgrind: Fix for automake update (2012-01-04 16:04:08 +0000)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib nitin/work
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=nitin/work
Nitin A Kamble (4):
python-pycairo: fix for x32
libevent: fix compilation for x32
libxxf86dga: fix compilation with x32 toolchain
vte: update patch header
.../python/python-pycairo_1.10.0.bb | 6 +-
.../libxxf86dga-1.1.2_fix_for_x32.patch | 30 ++++++++++++
.../recipes-graphics/xorg-lib/libxxf86dga_1.1.2.bb | 5 ++-
.../libevent/libevent-2.0.16_fix_for_x32.patch | 47 ++++++++++++++++++++
meta/recipes-support/libevent/libevent_2.0.16.bb | 5 +-
meta/recipes-support/vte/vte/introspection.patch | 8 +++
6 files changed, 95 insertions(+), 6 deletions(-)
create mode 100644 meta/recipes-graphics/xorg-lib/libxxf86dga/libxxf86dga-1.1.2_fix_for_x32.patch
create mode 100644 meta/recipes-support/libevent/libevent/libevent-2.0.16_fix_for_x32.patch
--
1.7.6.4
next reply other threads:[~2012-01-05 1:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 1:02 nitin.a.kamble [this message]
2012-01-05 1:02 ` [PATCH 1/4] python-pycairo: fix for x32 nitin.a.kamble
2012-01-05 1:02 ` [PATCH 2/4] libevent: fix compilation " nitin.a.kamble
2012-01-05 1:02 ` [PATCH 3/4] libxxf86dga: fix compilation with x32 toolchain nitin.a.kamble
2012-01-05 20:48 ` Khem Raj
2012-01-06 18:27 ` Kamble, Nitin A
2012-01-21 23:26 ` Khem Raj
2012-01-05 1:02 ` [PATCH 4/4] vte: update patch header nitin.a.kamble
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.1325725256.git.nitin.a.kamble@intel.com \
--to=nitin.a.kamble@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