All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>, Yu Zhiguo <yuzg@cn.fujitsu.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: xl: Enable 'xl console' in 'x86_64'
Date: Thu, 29 Apr 2010 11:40:30 -0700	[thread overview]
Message-ID: <C7FF20AE.11827%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <C7FF15D1.11818%keir.fraser@eu.citrix.com>

On 29/04/2010 10:54, "Keir Fraser" <keir.fraser@eu.citrix.com> wrote:

>> 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. ;-)

Now applied as xen-unstable:21237:a167ea374f26

 -- Keir

      reply	other threads:[~2010-04-29 18:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-28 10:29 xl: Enable 'xl console' in 'x86_64' Yu Zhiguo
2010-04-28 15:40 ` Jeremy Fitzhardinge
2010-04-29  2:38   ` Yu Zhiguo
2010-04-29 16:38     ` Jeremy Fitzhardinge
2010-04-29 17:54       ` Keir Fraser
2010-04-29 18:40         ` Keir Fraser [this message]

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=C7FF20AE.11827%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=jeremy@goop.org \
    --cc=xen-devel@lists.xensource.com \
    --cc=yuzg@cn.fujitsu.com \
    /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.