From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: xl: Enable 'xl console' in 'x86_64'
Date: Thu, 29 Apr 2010 10:54:09 -0700
Message-ID: <C7FF15D1.11818%keir.fraser@eu.citrix.com>
References: <4BD9B61F.9030204@goop.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <4BD9B61F.9030204@goop.org>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Jeremy Fitzhardinge <jeremy@goop.org>, Yu Zhiguo <yuzg@cn.fujitsu.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

On 29/04/2010 09:38, "Jeremy Fitzhardinge" <jeremy@goop.org> wrote:

>> Thanks for you reply. I think just look up both location is better.
> 
> Hm, I think just installing xenconsole (and the other executables) in a
> consistent (architecture-independent) place is a better long-term fix.
> That said, hard-coding paths like this seems like it would be awkward
> for anyone packaging this stuff (I think distros would prefer to put
> this kind of thing in /usr/libexec?).

The build system knows where it is installing stuff. The answer here is to
push the paths from the build system into a header file, then we will also
work with non-standard install prefixes and the like. Kind of like what xend
does with util/auxbin.py, but we don't need something as complex as that. I
will pick up this work item myself, since it is very simple. ;-)

 -- Keir