xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Juergen Gross <jgross@suse.com>
Cc: samuel.thibault@ens-lyon.org, Wei Liu <wei.liu2@citrix.com>,
	xen-devel@lists.xen.org
Subject: Re: [PATCH] stubdom: simplify and fix Makefile
Date: Fri, 4 Nov 2016 14:31:58 +0000	[thread overview]
Message-ID: <20161104143158.GL30231@citrix.com> (raw)
In-Reply-To: <125f0792-258f-c1f8-6778-faba216927f5@suse.com>

On Fri, Nov 04, 2016 at 03:29:01PM +0100, Juergen Gross wrote:
> On 04/11/16 15:20, Wei Liu wrote:
> > On Fri, Nov 04, 2016 at 10:53:29AM +0100, Juergen Gross wrote:
> >> The stubdom Makefile is setting up links for various libraries. This
> >> is done only once when qemu links are created and each library's links
> >> are updated/created only if the link for the Makefile of the library
> >> isn't already existing. In case a source is added to one library after
> >> doing the first make of stubdom the new source won't be linked by a
> >> new call of make.
> >>
> > 
> > I think this is a bug, hence I intend to take this patch in 4.8.
> 
> I wouldn't mind. OTOH this bug will surface only when modifying the
> code, so it isn't a severe one. Normally you'll notice a build error
> which will be gone after cleaning the tree.
> 

Alright. If you don't feel strongly about this, I'm fine with putting it
to my -next branch, too.

> 
> Juergen
> 
> > 
> >> Instead of testing the existence of the Makefile link use a make
> >> dependency which will catch changes of the linked Makefile, too.
> >>
> >> At the same time don't repeat the same link pattern 7 times but use a
> >> make macro to do the linking.
> >>
> >> Signed-off-by: Juergen Gross <jgross@suse.com>
> >> ---
> >>  stubdom/Makefile | 77 ++++++++++++++++++++++++++------------------------------
> >>  1 file changed, 35 insertions(+), 42 deletions(-)
> >>
> >> diff --git a/stubdom/Makefile b/stubdom/Makefile
> >> index 2921f30..9b30b58 100644
> >> --- a/stubdom/Makefile
> >> +++ b/stubdom/Makefile
> >> @@ -305,7 +305,41 @@ ioemu/linkfarm.stamp:
> >>  	touch ioemu/linkfarm.stamp
> >>  endif
> >>  
> >> -mk-headers-$(XEN_TARGET_ARCH): $(IOEMU_LINKFARM_TARGET)
> >> +define do_links
> >> +  touch $@
> > 
> > This should be moved to the last line of this macro.
> > 
> > If you agree on this, I can fix it up while committing.
> > 

What about this comment?

Wei.

> >> +  mkdir -p $(dir $@)include
> >> +  cd $(dir $@); \
> >> +  ln -sf $(dir $<)include/*.h include/; \
> >> +  ln -sf $(dir $<)*.[ch] .; \
> >> +  ln -sf $(dir $<)Makefile .
> >> +endef
> >> +
> > 
> > Wei.
> > 
> 

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2016-11-04 14:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-04  9:53 [PATCH] stubdom: simplify and fix Makefile Juergen Gross
2016-11-04  9:56 ` Samuel Thibault
2016-11-04 14:20 ` Wei Liu
2016-11-04 14:29   ` Juergen Gross
2016-11-04 14:31     ` Wei Liu [this message]
2016-11-04 14:44       ` Juergen Gross
2016-11-04 14:59         ` Wei Liu

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=20161104143158.GL30231@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=jgross@suse.com \
    --cc=samuel.thibault@ens-lyon.org \
    --cc=xen-devel@lists.xen.org \
    /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).