Openembedded Core Discussions
 help / color / mirror / Atom feed
From: nitin.a.kamble@intel.com
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/7] Misc Fixes
Date: Thu,  5 Jan 2012 09:30:44 -0800	[thread overview]
Message-ID: <cover.1325784550.git.nitin.a.kamble@intel.com> (raw)

From: Nitin A Kamble <nitin.a.kamble@intel.com>


Here are fixes related to x32 & automake-1.11.2.

Thanks,
Nitin

The following changes since commit 7f837eb05f924996c89283ec8b74e46f6b5cd343:

  bitbake/runqueue: Improve the setscene logging (2012-01-05 13:04:19 +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 (7):
  python-pycairo: fix for x32
  libevent: fix compilation for x32
  libxxf86dga: fix compilation with x32 toolchain
  vte: update patch header
  automake-1.11.2: backport pkglibexec_SCRIPTS fix
  mc: remove not needed fix for automake 1.11.2
  systemtap: remove not needed fix for automake 1.11.2

 ...utomake_1.11.2_fix_for_pkglibexec_SCRIPTS.patch |  118 ++++++++++++++++++++
 meta/recipes-devtools/automake/automake_1.11.2.bb  |    5 +-
 .../python/python-pycairo_1.10.0.bb                |    6 +-
 .../mc/files/fix_for_automake_1.11.2.patch         |   69 ------------
 meta/recipes-extended/mc/mc_4.8.1.bb               |    3 +-
 .../libxxf86dga-1.1.2_fix_for_x32.patch            |   30 +++++
 .../recipes-graphics/xorg-lib/libxxf86dga_1.1.2.bb |    5 +-
 .../systemtap/fix_for_automake_1.11.2.patch        |   46 --------
 meta/recipes-kernel/systemtap/systemtap_git.bb     |    6 +-
 .../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 ++
 12 files changed, 219 insertions(+), 129 deletions(-)
 create mode 100644 meta/recipes-devtools/automake/automake/automake_1.11.2_fix_for_pkglibexec_SCRIPTS.patch
 delete mode 100644 meta/recipes-extended/mc/files/fix_for_automake_1.11.2.patch
 create mode 100644 meta/recipes-graphics/xorg-lib/libxxf86dga/libxxf86dga-1.1.2_fix_for_x32.patch
 delete mode 100644 meta/recipes-kernel/systemtap/systemtap/fix_for_automake_1.11.2.patch
 create mode 100644 meta/recipes-support/libevent/libevent/libevent-2.0.16_fix_for_x32.patch

-- 
1.7.6.4




             reply	other threads:[~2012-01-05 17:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-05 17:30 nitin.a.kamble [this message]
2012-01-05 17:30 ` [PATCH 1/7] python-pycairo: fix for x32 nitin.a.kamble
2012-01-05 17:30 ` [PATCH 2/7] libevent: fix compilation " nitin.a.kamble
2012-01-05 17:30 ` [PATCH 3/7] libxxf86dga: fix compilation with x32 toolchain nitin.a.kamble
2012-01-05 17:30 ` [PATCH 4/7] vte: update patch header nitin.a.kamble
2012-01-05 17:30 ` [PATCH 5/7] automake-1.11.2: backport pkglibexec_SCRIPTS fix nitin.a.kamble
2012-01-05 17:30 ` [PATCH 6/7] mc: remove not needed fix for automake 1.11.2 nitin.a.kamble
2012-01-05 17:30 ` [PATCH 7/7] systemtap: " nitin.a.kamble
2012-01-09  5:26 ` [PATCH 0/7] Misc Fixes Saul Wold
  -- strict thread matches above, loose matches on Subject: below --
2012-05-02 20:53 [PATCH 0/7] Misc fixes Khem Raj
2012-05-09 23:39 ` 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.1325784550.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