On Tue, Nov 16, 2010 at 06:54:57PM +0000, Peter Maydell wrote: > On 16 November 2010 18:10, Anthony Liguori <anth...@codemonkey.ws> wrote: > > On 11/16/2010 11:43 AM, Peter Maydell wrote: > >> Unfortunately these commits: > >> 2834c3e Add support for generating a systemtap tapset static probes > >> 4addb11 Add a DTrace tracing backend targetted for SystemTAP compatability > > > > What's your configure output? > > I've attached it; the trace related bits are: > Trace backend nop > Trace output file trace-<pid> > > > I don't have the right environment to build with systemtap support, but > > --trace-backend=nop should work regardless. > > I'm using the nop backend, yes. > > I think the problem is that commit 2834c3e adds a target 'trace:' to the > Makefile.target which looks like it's intended to be a phony target. However > it isn't marked as such, so make actually tries to create a binary 'trace' > by falling back to its default rules (since there's a "trace.c" in the root > directory):
This Makefile problem was fixed in the v6 patches I posted on Nov 12th http://lists.gnu.org/archive/html/qemu-devel/2010-11/msg01033.html Unfortunately the v5 patches were applied by mistake. Regards, Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://deltacloud.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
