From: Ian Campbell <Ian.Campbell@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: Ian Jackson <ian.jackson@eu.citrix.com>, xen-devel@lists.xen.org
Subject: Re: [PATCH 1/2] libxl: don't delete xenlight.pc.in when cleaning
Date: Tue, 20 Jan 2015 11:53:39 +0000 [thread overview]
Message-ID: <1421754819.10440.241.camel@citrix.com> (raw)
In-Reply-To: <1421753352-30798-2-git-send-email-wei.liu2@citrix.com>
On Tue, 2015-01-20 at 11:29 +0000, Wei Liu wrote:
> That file is generated by configure. Deleting it leads to rerun
> configure after every 'make clean'.
Can you move it to distclean then please. With that:
Acked-by: Ian Campbell <ian.campbell@citrix.com>
> Signed-off-by: Wei Liu <wei.liu2@citrix.com>
> Cc: Ian Campbell <ian.campbell@citrix.com>
> Cc: Ian Jackson <ian.jackson@eu.citrix.com>
> ---
> tools/libxl/Makefile | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/libxl/Makefile b/tools/libxl/Makefile
> index 08fe814..9f36924 100644
> --- a/tools/libxl/Makefile
> +++ b/tools/libxl/Makefile
> @@ -282,7 +282,7 @@ clean:
> $(RM) -f _*.h *.o *.so* *.a $(CLIENTS) $(DEPS)
> $(RM) -f _*.c *.pyc _paths.*.tmp _*.api-for-check
> $(RM) -f testidl.c.new testidl.c *.api-ok
> - $(RM) -f xenlight.pc xenlight.pc.in
> + $(RM) -f xenlight.pc
>
> distclean: clean
>
next prev parent reply other threads:[~2015-01-20 11:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 11:29 [PATCH 0/2] libxl: two pkg-config related patches Wei Liu
2015-01-20 11:29 ` [PATCH 1/2] libxl: don't delete xenlight.pc.in when cleaning Wei Liu
2015-01-20 11:53 ` Ian Campbell [this message]
2015-01-20 14:46 ` Ian Jackson
2015-01-20 11:29 ` [PATCH 2/2] libxl: provide xlutil.pc Wei Liu
2015-01-20 11:54 ` Ian Campbell
2015-01-20 14:47 ` Ian Jackson
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=1421754819.10440.241.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=wei.liu2@citrix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.