From: Christoph Egger <Christoph.Egger@amd.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH] tools: use PREFIX when building upstream qemu
Date: Fri, 26 Oct 2012 13:09:07 +0200 [thread overview]
Message-ID: <508A6F53.9000700@amd.com> (raw)
In-Reply-To: <1351246518.15162.23.camel@zakaz.uk.xensource.com>
On 10/26/12 12:15, Ian Campbell wrote:
> On Fri, 2012-10-26 at 10:47 +0100, Christoph Egger wrote:
>> On 10/25/12 14:39, Ian Jackson wrote:
>>> Christoph Egger writes ("[Xen-devel] [PATCH] tools: use PREFIX when building upstream qemu"):
>>>>
>>>> use PREFIX when building upstream qemu.
>>>>
>>>> Signed-off-by: Christoph Egger <Christoph.Egger@amd.com>
>>>
>>> This looks reasonable but can you explain what goes wrong when,
>>> without this ? I'd like to be able to verify the bug and fix myself.
>>
>> qemu's configure assumes /usr/local as prefix by default, otherwise.
>> With this patch, qemu config files and manpages are installed under
>> the specified $(PREFIX).
>
> Is that what we want?
Yes, we want everything that is not explicitely specified
to configure under $(PREFIX).
Christoph
> Or do we want our version of qemu to be
> under /usr/lib/xen?
next prev parent reply other threads:[~2012-10-26 11:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-25 10:38 [PATCH] tools: use PREFIX when building upstream qemu Christoph Egger
2012-10-25 12:39 ` Ian Jackson
2012-10-26 9:47 ` Christoph Egger
2012-10-26 10:15 ` Ian Campbell
2012-10-26 11:09 ` Christoph Egger [this message]
2012-12-13 10:40 ` Ian Campbell
2012-12-13 14:22 ` Christoph Egger
2012-12-13 14:25 ` Ian Jackson
2012-12-13 14:41 ` Christoph Egger
2012-12-13 15:07 ` Ian Jackson
2013-01-10 21:50 ` Christoph Egger
2012-12-13 14:28 ` 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=508A6F53.9000700@amd.com \
--to=christoph.egger@amd.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).