From: nitin.a.kamble@intel.com
To: openembedded-core@lists.openembedded.org, eric@eukrea.com,
fcooper@ti.com, Martin.Jansa@gmail.com,
richard.purdie@linuxfoundation.org
Subject: [PATCH 0/1] fix for the sdk gdb issue
Date: Wed, 21 Mar 2012 09:35:12 -0700 [thread overview]
Message-ID: <cover.1332347414.git.nitin.a.kamble@intel.com> (raw)
From: Nitin A Kamble <nitin.a.kamble@intel.com>
This reverts the commit for adding python support to sdk gdb. It is
breaking the sdk gdb as reported in this bug:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=2077
The following changes since commit 40f95685e6a3b4359d2ab2fea1418fe5e4bd0aa1:
gzip/pigz-native: Install into a prefix to avoid clashing with system binaries (2012-03-21 15:33:07 +0000)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib nitin/bugfix
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=nitin/bugfix
Nitin A Kamble (1):
Revert "gdb-cross-canadian: build gdb with python support"
meta/recipes-devtools/gdb/gdb-cross-canadian.inc | 20 +-------------------
.../recipes-devtools/gdb/gdb-cross-canadian_7.4.bb | 2 +-
2 files changed, 2 insertions(+), 20 deletions(-)
--
1.7.6.4
next reply other threads:[~2012-03-21 16:44 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 16:35 nitin.a.kamble [this message]
2012-03-21 16:35 ` [PATCH 1/1] Revert "gdb-cross-canadian: build gdb with python support" nitin.a.kamble
2012-03-21 17:07 ` Eric Bénard
2012-03-21 17:47 ` Kamble, Nitin A
2012-03-21 17:52 ` Eric Bénard
2012-03-21 17:57 ` Kamble, Nitin A
2012-03-21 18:02 ` Eric Bénard
2012-03-21 18:07 ` Kamble, Nitin A
2012-03-21 19:32 ` Eric Bénard
2012-03-21 19:49 ` Martin Jansa
2012-03-21 20:48 ` Kamble, Nitin A
2012-03-21 21:02 ` Eric Bénard
2012-03-21 21:12 ` Kamble, Nitin A
2012-03-21 21:35 ` Eric Bénard
2012-03-21 21:53 ` Kamble, Nitin A
2012-03-21 22:05 ` Eric Bénard
2012-03-21 22:10 ` Kamble, Nitin A
2012-03-21 22:21 ` Saul Wold
2012-03-21 22:37 ` Eric Bénard
2012-03-21 22:55 ` Kamble, Nitin A
2012-03-21 23:07 ` Kamble, Nitin A
2012-03-22 12:09 ` Eric Bénard
2012-03-21 22:22 ` Kamble, Nitin A
2012-03-22 8:47 ` Martin Jansa
2012-03-22 8:50 ` Eric Bénard
2012-03-22 0:27 ` Khem Raj
2012-03-22 1:58 ` Kamble, Nitin A
2012-03-22 4:24 ` Khem Raj
2012-03-22 4:55 ` Kamble, Nitin A
2012-03-22 5:06 ` Khem Raj
2012-03-22 5:42 ` Khem Raj
2012-03-22 12:13 ` Eric Bénard
2012-03-22 12:17 ` Khem Raj
2012-03-22 12:43 ` Eric Bénard
2012-03-22 12:57 ` Khem Raj
2012-03-22 13:14 ` Eric Bénard
2012-03-22 13:34 ` Eric Bénard
2012-03-22 13:54 ` Khem Raj
2012-03-22 16:20 ` Kamble, Nitin A
2012-03-22 16:38 ` Khem Raj
2012-03-22 17:38 ` Kamble, Nitin A
2012-03-22 19:16 ` Khem Raj
2012-03-22 21:31 ` Eric Bénard
2012-03-22 21:40 ` Kamble, Nitin A
2012-03-23 8:07 ` Eric Bénard
2012-03-22 21:48 ` Kamble, Nitin A
2012-03-23 5:33 ` Khem Raj
2012-03-23 6:29 ` Khem Raj
2012-03-23 7:12 ` Khem Raj
2012-03-23 8:31 ` Eric Bénard
2012-03-23 12:07 ` Khem Raj
2012-03-23 16:07 ` Kamble, Nitin A
2012-03-21 22:04 ` Kamble, Nitin A
2012-03-21 22:09 ` Eric Bénard
2012-03-21 23:25 ` Kamble, Nitin A
2012-03-21 23:29 ` Richard Purdie
2012-03-21 21:48 ` Kamble, Nitin A
2012-03-21 19:04 ` Kamble, Nitin A
2012-03-21 19:36 ` Eric Bénard
2012-03-21 19:48 ` Kamble, Nitin A
2012-03-21 17:58 ` Martin Jansa
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.1332347414.git.nitin.a.kamble@intel.com \
--to=nitin.a.kamble@intel.com \
--cc=Martin.Jansa@gmail.com \
--cc=eric@eukrea.com \
--cc=fcooper@ti.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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