xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: "Cédric Bosdonnat" <cbosdonnat@suse.com>
Cc: Juergen Gross <jgross@suse.com>, Wei Liu <wei.liu2@citrix.com>,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	xen-devel@lists.xen.org
Subject: Re: [PATCH v2] libxl: fix gentypes call in Makefile
Date: Fri, 11 Nov 2016 02:22:23 +0000	[thread overview]
Message-ID: <20161111022223.GJ31926@citrix.com> (raw)
In-Reply-To: <20161110164600.29851-1-cbosdonnat@suse.com>

On Thu, Nov 10, 2016 at 05:46:00PM +0100, Cédric Bosdonnat wrote:
> From the make documentation:
> 
> "$* [...] If the target is `dir/a.foo.b' and the target pattern is
> `a.%.b' then the stem is `dir/foo'. In a static pattern rule, the
> stem is part of the file name that matched the `%' in the target
> pattern."
> 
> The rule generating the c types files from the idl ones is not
> a static pattern rule, but rather an implicit rule. Thus the value
> of $* is preceded by the file path, instead of only what matches %.
> 
> In order to get this fixed, drop the path using a $(notdir $*).
> 
> Signed-off-by: Cédric Bosdonnat <cbosdonnat@suse.com>

OOI how did you discover this? Should we consider backporting this to
some older versions?

> ---
>   v2: use $(notdir $*) instead of $(shell basename $*)
> ---
>  tools/libxl/Makefile | 13 +++++++------
>  1 file changed, 7 insertions(+), 6 deletions(-)
> 
> diff --git a/tools/libxl/Makefile b/tools/libxl/Makefile
> index af0a3ad..4dbaa98 100644
> --- a/tools/libxl/Makefile
> +++ b/tools/libxl/Makefile
> @@ -250,12 +250,13 @@ $(LIBXL_OBJS) $(LIBXL_TEST_OBJS) $(LIBXLU_OBJS) \
>  $(LIBXL_OBJS) $(LIBXL_TEST_OBJS): libxl_internal.h
>  
>  _libxl_type%.h _libxl_type%_json.h _libxl_type%_private.h _libxl_type%.c: libxl_type%.idl gentypes.py idl.py
> -	$(PYTHON) gentypes.py libxl_type$*.idl __libxl_type$*.h __libxl_type$*_private.h \
> -		__libxl_type$*_json.h  __libxl_type$*.c
> -	$(call move-if-changed,__libxl_type$*.h,_libxl_type$*.h)
> -	$(call move-if-changed,__libxl_type$*_private.h,_libxl_type$*_private.h)
> -	$(call move-if-changed,__libxl_type$*_json.h,_libxl_type$*_json.h)
> -	$(call move-if-changed,__libxl_type$*.c,_libxl_type$*.c)
> +	$(eval stem = $(notdir $*))
> +	$(PYTHON) gentypes.py libxl_type$(stem).idl __libxl_type$(stem).h __libxl_type$(stem)_private.h \
> +		__libxl_type$(stem)_json.h  __libxl_type$(stem).c
> +	$(call move-if-changed,__libxl_type$(stem).h,_libxl_type$(stem).h)
> +	$(call move-if-changed,__libxl_type$(stem)_private.h,_libxl_type$(stem)_private.h)
> +	$(call move-if-changed,__libxl_type$(stem)_json.h,_libxl_type$(stem)_json.h)
> +	$(call move-if-changed,__libxl_type$(stem).c,_libxl_type$(stem).c)
>  
>  libxenlight.so: libxenlight.so.$(MAJOR)
>  	$(SYMLINK_SHLIB) $< $@
> -- 
> 2.10.1
> 

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

  reply	other threads:[~2016-11-11  2:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-10 16:46 [PATCH v2] libxl: fix gentypes call in Makefile Cédric Bosdonnat
2016-11-11  2:22 ` Wei Liu [this message]
2016-11-14  8:17   ` Cedric Bosdonnat
2016-12-12  9:46 ` 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=20161111022223.GJ31926@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=cbosdonnat@suse.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jgross@suse.com \
    --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).