All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Egger <Christoph_Egger@gmx.de>
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: Thu, 13 Dec 2012 15:22:20 +0100	[thread overview]
Message-ID: <50C9E49C.8050809@gmx.de> (raw)
In-Reply-To: <1355395238.10554.71.camel@zakaz.uk.xensource.com>

On 13.12.12 11:40, Ian Campbell wrote:

> Adding Christoph's new address, I guess this is a thing exposed on
> NetBSD?


This is not specific to NetBSD. It is exposed everywhere where you
install Xen into a non-default directory by specifying the prefix
to configure.

Christoph

>
> On Thu, 2012-10-25 at 13:39 +0100, 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.
>
> AFAICT the default PREFIX for qemu-xen is /usr/local and we pass
> --bindir, --datadir (as Xen specific paths, like /usr/lib/xen/bin) but
> not --prefix. It looks like this covers most stuff but results in a
> smattering of stuff getting installed under /usr/local:
>
> $ find dist/install/usr/local/ | grep qemu
> dist/install/usr/local/libexec/qemu-bridge-helper
> dist/install/usr/local/share/man/man8/qemu-nbd.8
> dist/install/usr/local/share/man/man1/qemu.1
> dist/install/usr/local/share/man/man1/qemu-img.1
> dist/install/usr/local/share/doc/qemu
> dist/install/usr/local/share/doc/qemu/qemu-tech.html
> dist/install/usr/local/share/doc/qemu/qemu-doc.html
> dist/install/usr/local/share/doc/qemu/qmp-commands.txt
> dist/install/usr/local/etc/qemu
> dist/install/usr/local/etc/qemu/target-x86_64.conf
> (there is also some ocaml stuff under there it seems...)
>
> I'm not quite sure that installing those into our $PREFIX is correct
> either though -- there seems like the possibility of clashing with a
> non-Xen install of qemu, so we might be better off moving these to e.g.
> $PREFIX/doc/xen/qemu/ and adding "xen" in the man page path etc? (the
> binaries corresponding to those manpages are in /usr/lib/xen/bin/)
> Perhaps qemu.1xen ?
>
> I don't know what dist/install/usr/local/etc/qemu/target-x86_64.conf is
> but it is empty here. I suspect Xen does not use
> dist/install/usr/local/libexec/qemu-bridge-helper or it should be
> in /usr/lib/xen/bin.
>
> Ian.
>

  reply	other threads:[~2012-12-13 14:22 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
2012-12-13 10:40   ` Ian Campbell
2012-12-13 14:22     ` Christoph Egger [this message]
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=50C9E49C.8050809@gmx.de \
    --to=christoph_egger@gmx.de \
    --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 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.