From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Eric Bénard" <eric@eukrea.com>
Cc: Martin Jansa <martin.jansa@gmail.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] Revert "gdb-cross-canadian: build gdb with python support"
Date: Wed, 21 Mar 2012 23:29:49 +0000 [thread overview]
Message-ID: <1332372589.9740.225.camel@ted> (raw)
In-Reply-To: <20120321230914.37861302@eb-e6520>
Sorry to interject into the middle of this but I have a sudden idea. I
suspect Nitin is using rpm and the people with successful builds are
using ipk.
Further, I suspect that rpm is including python-nativesdk whilst the ipk
version might not be due to its slightly better dependency detection.
So this could be something wrong with the python-nativesdk.
I'd be interested to see if this fails for Martin/Eric if they manually
include python-nativesdk. Nitin, you could also try an ipk build.
Cheers,
Richard
next prev parent reply other threads:[~2012-03-21 23:41 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 16:35 [PATCH 0/1] fix for the sdk gdb issue nitin.a.kamble
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2012-03-23 16:36 Khem Raj
2012-03-23 17:01 ` Kamble, Nitin A
2012-03-23 17:44 ` Richard Purdie
2012-03-23 18:01 ` Khem Raj
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=1332372589.9740.225.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=eric@eukrea.com \
--cc=martin.jansa@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.