qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: kwolf@redhat.com, qemu-block@nongnu.org,
	Jeff Cody <jcody@redhat.com>,
	qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH for-2.9] mirror: Fix backwards mirror_yield parameters
Date: Wed, 15 Mar 2017 10:59:24 +0000	[thread overview]
Message-ID: <20170315105924.GH7770@redhat.com> (raw)
In-Reply-To: <20170315102644.GF7770@redhat.com>

On Wed, Mar 15, 2017 at 10:26:44AM +0000, Daniel P. Berrange wrote:
> On Wed, Mar 15, 2017 at 06:18:35PM +0800, Stefan Hajnoczi wrote:
> > On Fri, Mar 10, 2017 at 02:49:22PM -0600, Eric Blake wrote:
> > > And here's where I'm stuck: the makefiles are broken.  Touching
> > > scripts/tracetool/format/h.py does NOT cause tracetool to be re-run by a
> > > mere 'make'; I've had to resort to 'make -B block/trace.h-timestamp' to
> > > get things to rebuild.  And this is in spite of the fact that h.py
> > > _should_ be getting listed in $(tracetool-y) by trace/Makefile.objs, and
> > > $(tracetool-y) is listed as a dependency of %/trace.h-timestamp in the
> > > top-level Makefile.  I would appreciate anyone with advice or an idea on
> > > how to patch Makefile to get the dependency working without me having to
> > > manually kick it.
> > 
> > Also CCing Daniel Berrange.  He recently touched the tracing Makefiles
> > and may have ideas.
> 
> I've been looking at this and I'm damned if I understand what's broken.
> All the required dependancies look to be expressed in the Makefile
> 
>   %/trace.h: %/trace.h-timestamp
>   %/trace.h-timestamp: $(SRC_PATH)/%/trace-events $(tracetool-y)
> 
> and $(tracetool-y) expands to the list of source files
> 
>   tracetool-y = $(SRC_PATH)/scripts/tracetool.py
>   tracetool-y += $(shell find $(SRC_PATH)/scripts/tracetool -name "*.py")
> 
> 
> If I do 'touch hw/net/trace-events', then hw/net/trace.h gets rebuilt,
> but if do 'touch scripts/tracetool.py' it doesn't get built. So somehow
> make seems to be dropping the $(tracetool-y) deps despite being listed
> against the %/trace-h-timestamp file, and despite earlier deps on
> trace-events being honoured

Oh this is a fun one.  While the $(tracetool-y) variable *is* defined at
the time the build rules execute, it is *not* defined at the time make
evaluates dependancies, so it expanded to be empty ! I copied you on
the easy fix

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/ :|

  reply	other threads:[~2017-03-15 10:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-10  3:15 [Qemu-devel] [PATCH for-2.9] mirror: Fix backwards mirror_yield parameters Eric Blake
2017-03-10  3:25 ` Eric Blake
2017-03-10 20:49   ` Eric Blake
2017-03-15 10:18     ` Stefan Hajnoczi
2017-03-15 10:26       ` Daniel P. Berrange
2017-03-15 10:59         ` Daniel P. Berrange [this message]
2017-03-16  2:21           ` 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=20170315105924.GH7770@redhat.com \
    --to=berrange@redhat.com \
    --cc=jcody@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.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 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).