From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Xen-devel <xen-devel@lists.xen.org>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: [PATCH] tools/libxl: Fix build of libxl with ./configure --disable-blktap2
Date: Wed, 3 Sep 2014 17:29:06 +0100 [thread overview]
Message-ID: <540741D2.3060903@citrix.com> (raw)
In-Reply-To: <1408113177-10339-1-git-send-email-andrew.cooper3@citrix.com>
On 15/08/14 15:32, Andrew Cooper wrote:
> Autoconf already has appropriate Linux/non-Linux logic for CONFIG_BLKTAP2.
>
> Let LIBXL_BLKTAP inherit directly from CONFIG_BLKTAP2, rather than requiring a
> further LIBXL_BLKTAP=n in addition to ./configure --disable-blktap2 to get
> libxl to successfully link under Linux.
>
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
> CC: Ian Campbell <Ian.Campbell@citrix.com>
> CC: Ian Jackson <Ian.Jackson@eu.citrix.com>
Ping?
> ---
> tools/Rules.mk | 6 +-----
> 1 file changed, 1 insertion(+), 5 deletions(-)
>
> diff --git a/tools/Rules.mk b/tools/Rules.mk
> index 5bac700..fa59365 100644
> --- a/tools/Rules.mk
> +++ b/tools/Rules.mk
> @@ -55,11 +55,7 @@ CFLAGS_libxenvchan = -I$(XEN_LIBVCHAN)
> LDLIBS_libxenvchan = $(SHLIB_libxenctrl) $(SHLIB_libxenstore) -L$(XEN_LIBVCHAN) -lxenvchan
> SHLIB_libxenvchan = -Wl,-rpath-link=$(XEN_LIBVCHAN)
>
> -ifeq ($(CONFIG_Linux),y)
> -LIBXL_BLKTAP ?= y
> -else
> -LIBXL_BLKTAP ?= n
> -endif
> +LIBXL_BLKTAP ?= $(CONFIG_BLKTAP2)
>
> ifeq ($(LIBXL_BLKTAP),y)
> CFLAGS_libblktapctl = -I$(XEN_BLKTAP2)/control -I$(XEN_BLKTAP2)/include $(CFLAGS_xeninclude)
next prev parent reply other threads:[~2014-09-03 16:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-15 14:32 [PATCH] tools/libxl: Fix build of libxl with ./configure --disable-blktap2 Andrew Cooper
2014-09-03 16:29 ` Andrew Cooper [this message]
2014-09-08 11:10 ` 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=540741D2.3060903@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.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 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).