From: "Daniel P. Berrange" <berrange@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] trace: ensure $(tracetool-y) is defined in top level makefile
Date: Wed, 15 Mar 2017 11:46:23 +0000 [thread overview]
Message-ID: <20170315114623.GI7770@redhat.com> (raw)
In-Reply-To: <de695865-d569-916d-218e-1faff31d6f4b@redhat.com>
On Wed, Mar 15, 2017 at 06:44:25AM -0500, Eric Blake wrote:
> On 03/15/2017 05:56 AM, Daniel P. Berrange wrote:
> > The build rules for trace files have a dependancy on $(tracetool-y).
> > This variable populated in the trace/Makefile.objs file and thus its
> > definition gets pulled into the top level makefile. This happens too
> > late in the process though, so by the time $(tracetool-y) is defined,
> > make has already evaluated $(tracetool-y) in the dependancies and
> > found it to be empty. The result is that when the tracetool source
> > is changed, the generated files are not rebuilt. The solution is to
> > define the variable in the top level makefile too
> >
> > Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
> > ---
> > Makefile | 3 +++
> > 1 file changed, 3 insertions(+)
>
> Does this mean the definitions in trace/Makefile.objs are now redundant
> and can be omitted?
Hmm, I'm not sure, but quite possibly true.
>
> >
> > diff --git a/Makefile b/Makefile
> > index 1c4c04f..dffc74b 100644
> > --- a/Makefile
> > +++ b/Makefile
> > @@ -85,6 +85,9 @@ GENERATED_SOURCES += $(TRACE_SOURCES)
> >
> > trace-group-name = $(shell dirname $1 | sed -e 's/[^a-zA-Z0-9]/_/g')
> >
> > +tracetool-y = $(SRC_PATH)/scripts/tracetool.py
> > +tracetool-y += $(shell find $(SRC_PATH)/scripts/tracetool -name "*.py")
>
> Should this also include the comment currently in trace/Makefile.objs:
>
> ######################################################################
> # tracetool source files
> # Every rule that invokes tracetool must depend on this so code is
> regenerated
> # if tracetool itself changes.
>
> But it certainly looks like you're on the right track for fixing the
> issue I ran into.
IMHO such comments are pointless - they're just stating the obvious.
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/ :|
prev parent reply other threads:[~2017-03-15 11:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 10:56 [Qemu-devel] [PATCH] trace: ensure $(tracetool-y) is defined in top level makefile Daniel P. Berrange
2017-03-15 11:44 ` Eric Blake
2017-03-15 11:46 ` Daniel P. Berrange [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=20170315114623.GI7770@redhat.com \
--to=berrange@redhat.com \
--cc=eblake@redhat.com \
--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).