From: "Daniel P. Berrange" <berrange@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: Greg Kurz <groug@kaod.org>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] trace: fix generated code build break
Date: Thu, 17 Nov 2016 14:25:43 +0000 [thread overview]
Message-ID: <20161117142543.GF28482@redhat.com> (raw)
In-Reply-To: <20161117142200.GG2058@lemon>
On Thu, Nov 17, 2016 at 10:22:00PM +0800, Fam Zheng wrote:
> On Thu, 11/17 14:59, Greg Kurz wrote:
> > If the QEMU source dir is
> >
> > /var/tmp/aaa-qemu-clone
> >
> > and the build dir is
> >
> > /var/tmp/qemu-aio-poll-v2
> >
> > Then I get an error as:
> >
> > trace/generated-tracers.c:15950:13: error: invalid suffix "_trace_events"
> > on integer constant
> > TraceEvent *2_trace_events[] = {
> > ^
> > trace/generated-tracers.c:15950:13: error: expected identifier or ‘(’ before
> > numeric constant
> > trace/generated-tracers.c: In function ‘trace_2_register_events’:
> > trace/generated-tracers.c:17949:32: error: invalid suffix "_trace_events" on
> > integer constant
> > trace_event_register_group(2_trace_events);
> > ^
> > make: *** [trace/generated-tracers.o] Error 1
> >
> > This patch fixes the issue.
> >
> > Reported-by: Fam Zheng <famz@redhat.com>
> > Signed-off-by: Greg Kurz <groug@kaod.org>
> > ---
> > scripts/tracetool.py | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/scripts/tracetool.py b/scripts/tracetool.py
> > index fe9c9e904b03..c9e47371d3c6 100755
> > --- a/scripts/tracetool.py
> > +++ b/scripts/tracetool.py
> > @@ -70,7 +70,7 @@ def make_group_name(filename):
> >
> > if dirname == "":
> > return "common"
> > - return re.sub(r"[^A-Za-z0-9]", "_", dirname)
> > + return "_" + re.sub(r"[^A-Za-z0-9]", "_", dirname)
> >
> > def main(args):
> > global _SCRIPT
> >
> >
>
> What make_group_name does here (returning substring of build dir based on source
> dir) doesn't make sense to me at all, maybe it's because the patchset Dan is
> working on was only partly merged. But as a bandage for 2.8, it makes things
> better on top of the previous attemp 630b210b9 'Fix build for less common build
> directories names'. Thanks!
As a quick hack for 2.8 this is fine by me. We can trivially revert it
after merging the rest of the patches in 2.9 if needed.
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://entangle-photo.org -o- http://search.cpan.org/~danberr/ :|
next prev parent reply other threads:[~2016-11-17 14:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 13:59 [Qemu-devel] [PATCH] trace: fix generated code build break Greg Kurz
2016-11-17 14:22 ` Fam Zheng
2016-11-17 14:25 ` Daniel P. Berrange [this message]
2016-11-17 14:44 ` Greg Kurz
2016-11-18 11:10 ` Stefan Hajnoczi
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=20161117142543.GF28482@redhat.com \
--to=berrange@redhat.com \
--cc=famz@redhat.com \
--cc=groug@kaod.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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.