From: Ian Campbell <Ian.Campbell@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: Olaf Hering <olaf@aepfle.de>,
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 10:06:31 +0000 [thread overview]
Message-ID: <1422266791.17434.0.camel@citrix.com> (raw)
In-Reply-To: <20150126100111.GA9708@zion.uk.xensource.com>
On Mon, 2015-01-26 at 10:01 +0000, Wei Liu wrote:
> On Mon, Jan 26, 2015 at 09:31:44AM +0100, Olaf Hering wrote:
> > On Sun, Jan 25, 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.
> >
> > Another one. I suspect there is more like that in qemu-xen-traditional.
> > Should I spent/waste my time to convert qemu-xen-traditional to handle
> > options via configure instead of relying on variables from the Xen
> > buildsystem? The same happend when my --prefix series was applied.
> >
>
> qemu-xen-traditional's configure is quite ancient I don't think that's
> worth it.
It's also not autoconf (neither is mainline qemu's AFAIK), it's just a
hand written shell script...
Ian.
next prev parent reply other threads:[~2015-01-26 10:06 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 [this message]
2015-01-26 9:55 ` Ian Campbell
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=1422266791.17434.0.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=olaf@aepfle.de \
--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.