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] tools/Makefile: fix qemu-xen-traditional build
Date: Mon, 26 Jan 2015 09:55:41 +0000 [thread overview]
Message-ID: <1422266141.10967.4.camel@citrix.com> (raw)
In-Reply-To: <1422200339-1020-1-git-send-email-wei.liu2@citrix.com>
On Sun, 2015-01-25 at 15:38 +0000, Wei Liu wrote:
> In d9740237a ("tools: unhook blktap1 from the build and remove all
> references to it"), one spot was left unchanged, which leads to failure
> in building qemu-xen-traditional.
Well spotted, which make invocation hits this path? make dist (what I
test) didn't.
> Signed-off-by: Wei Liu <wei.liu2@citrix.com>
> Cc: Ian Campbell <ian.campbell@citrix.com>
> Cc: Ian Jackson <ian.jackson@eu.citrix.com>
Acked-by: Ian Campbell <ian.campbell@citrix.com>
Should we be worried that the -all- and -install- targets are similar
but not identical? Specifically one of them lack --extra-cflags?
Perhaps we should refactor those so the options are only given ones?
> ---
> tools/Makefile | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tools/Makefile b/tools/Makefile
> index 1ad7a5d..5d7a75f 100644
> --- a/tools/Makefile
> +++ b/tools/Makefile
> @@ -158,6 +158,7 @@ qemu-xen-traditional-dir-force-update: qemu-xen-traditional-dir-find
> subdir-all-qemu-xen-traditional-dir: qemu-xen-traditional-dir-find
> set -e; \
> $(buildmakevars2shellvars); \
> + export CONFIG_BLKTAP1=n; \
> cd qemu-xen-traditional-dir; \
> $(QEMU_ROOT)/xen-setup \
> $(IOEMU_EXTRA_LDFLAGS) \
next prev parent reply other threads:[~2015-01-26 9:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-25 15:38 [PATCH] tools/Makefile: fix qemu-xen-traditional build Wei Liu
2015-01-26 8:31 ` Olaf Hering
2015-01-26 10:01 ` Wei Liu
2015-01-26 10:06 ` Ian Campbell
2015-01-26 9:55 ` Ian Campbell [this message]
2015-01-26 11:05 ` Wei Liu
2015-01-27 17:20 ` Ian Campbell
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=1422266141.10967.4.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.