Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Liang Li <liang.li@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] trace-cmd: Update for python-native changes
Date: Tue, 31 Jul 2012 12:08:40 +0100	[thread overview]
Message-ID: <1343732920.9526.4.camel@ted> (raw)
In-Reply-To: <1343697899-20776-1-git-send-email-liang.li@windriver.com>

On Tue, 2012-07-31 at 09:24 +0800, Liang Li wrote:
> Add pythonnative to the inherits list, otherwise we'll end up with
> compiling error like:
> 
> | swig -Wall -python -noproxy ctracecmd.i
> | trace-cmd.h:65: Error: Syntax error in input(1).
> | trace-cmd.h:221: Warning(322): Redundant redeclaration of
> | 'trace_util_ftrace_options',
> | trace-cmd.h:196: Warning(322): previous declaration of
> | 'trace_util_ftrace_options'.
> | parse-events.h:275: Warning(312): Nested union not currently
> | supported (ignored).
> | parse-events.h:707: Warning(312): Nested union not currently
> | supported (ignored).
> | parse-events.h:746: Warning(312): Nested union not currently
> | supported (ignored).
> | make: *** [ctracecmd.so] Segmentation fault
> 
> Signed-off-by: Liang Li <liang.li@windriver.com>
> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
> ---
> Hi all,
> 
> Due to recent change to python, we've done pythonnative related change to
> various recipes like perf, xcb etc. Now this one is for trace-cmd. :)
> 
> Thanks.
> 
>  meta/recipes-kernel/trace-cmd/trace-cmd_1.2.bb | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

I merged Morgan's patch for this.

Thanks,

Richard




  reply	other threads:[~2012-07-31 11:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-31  1:24 [PATCH] trace-cmd: Update for python-native changes Liang Li
2012-07-31 11:08 ` Richard Purdie [this message]
2012-07-31 13:35   ` Liang Li

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=1343732920.9526.4.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=liang.li@windriver.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