From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: vilanova@ac.upc.edu
Subject: Re: [Qemu-devel] [PATCH] trace: rebuild generated-events.o when configuration changes
Date: Mon, 11 Mar 2013 15:18:37 +0100 [thread overview]
Message-ID: <20130311141837.GA6880@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1362754335-4381-1-git-send-email-stefanha@redhat.com>
On Fri, Mar 08, 2013 at 03:52:15PM +0100, Stefan Hajnoczi wrote:
> Make sure to rebuild generated-events.o when ./configure options change.
> This prevents linker errors when a stale generated-events.o gets linked
> with code compiled against fresh headers. For example, try building
> with ./configure --enable-trace-backend=stderr followed by ./configure
> --enable-trace-backend=dtrace.
>
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> ---
> trace/Makefile.objs | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied to my tracing tree:
https://github.com/stefanha/qemu/commits/tracing
Stefan
prev parent reply other threads:[~2013-03-11 14:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-08 14:52 [Qemu-devel] [PATCH] trace: rebuild generated-events.o when configuration changes Stefan Hajnoczi
2013-03-11 14:18 ` Stefan Hajnoczi [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=20130311141837.GA6880@stefanha-thinkpad.redhat.com \
--to=stefanha@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=vilanova@ac.upc.edu \
/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;
as well as URLs for NNTP newsgroup(s).