From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Martin Jansa <martin.jansa@gmail.com>
Subject: Re: [RFC] gdb-cross: add pythonnative
Date: Tue, 07 Aug 2012 21:31:00 +0100 [thread overview]
Message-ID: <1344371460.9756.297.camel@ted> (raw)
In-Reply-To: <CAMKF1sosOY9Usa+MkWByQM51urYFUKLAqH-UE7y-J2tHfHSi=w@mail.gmail.com>
On Tue, 2012-08-07 at 13:15 -0700, Khem Raj wrote:
> On Tue, Aug 7, 2012 at 9:14 AM, Darren Hart <dvhart@linux.intel.com> wrote:
> >
> >> I fixed this properly by disabling python in gdb-cross.
>
> I think having python support would be desirable no ?
Perhaps, I didn't make a decision on that. Just inheriting pythonnative
isn't the correct way to do that, we need to make an explicit decision
and set the correct configure option so its clear what we're doing.
In the meantime I wasn't happy seeing build failures.
Cheers,
Richard
prev parent reply other threads:[~2012-08-07 20:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 1:26 [RFC] gdb-cross: add pythonnative Martin Jansa
2012-07-31 11:07 ` Richard Purdie
2012-07-31 11:10 ` Martin Jansa
2012-08-01 16:23 ` Darren Hart
2012-08-07 12:38 ` Richard Purdie
2012-08-07 16:14 ` Darren Hart
2012-08-07 20:15 ` Khem Raj
2012-08-07 20:31 ` Richard Purdie [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=1344371460.9756.297.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox