From: Christoph Egger <Christoph.Egger@amd.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Keir Fraser <Keir.Fraser@eu.citrix.com>
Subject: Re: Re: [PATCH] ioemu: Fixes for build/install system
Date: Tue, 5 May 2009 17:25:16 +0200 [thread overview]
Message-ID: <200905051725.16326.Christoph.Egger@amd.com> (raw)
In-Reply-To: <18944.19719.773562.537988@mariner.uk.xensource.com>
On Tuesday 05 May 2009 16:28:23 Ian Jackson wrote:
> Christoph Egger writes ("Re: [Xen-devel] Re: [PATCH] ioemu: Fixes for
build/install system"):
> > On Tuesday 05 May 2009 16:00:12 Ian Jackson wrote:
> > > Could you please do this in xen-setup-* instead, rather than in
> > > xen-unstable's Makefiles ? That (a) avoids coupling between the two
> > > repositories and (b) will mean that xen-setup will do the right thing
> > > when run by hand.
> >
> > I tried, but it doesn't work. It has to be set _before_ xen-setup* is
> > called for the same reason XEN_ROOT is set in xen-unstable's Makefiles.
>
> I don't understand, I'm afraid.
>
> XEN_ROOT needs to be handled the way it is because it's (a) available
> only as a make variable in the xen-unstable makefiles and (b) is a
> relative pathname so needs to be massaged for use by a sub-component.
> If you run xen-setup it guesses a value for XEN_ROOT which is right
> for at least one common case.
PREFIX is defined by xen build system as a make variable. xen's build system
runs some shell code to pass XEN_ROOT as a shell variable to xen-setup.
My patch adds some shell code to pass PREFIX as a shell variable to xen-setup,
too.
xen-setup can guess XEN_ROOT due to the directory structure
relative to xen's toplevel source directory. But how should xen-setup guess an
install directory ?
> PREFIX could be set in the environment perfectly well and doesn't need
> any massaging. You could just have xen-setup invent a default PREFIX
> if none was found in its environment.
No, this would end up in having different prefixes on NetBSD at least.
xen tools go to /usr/pkg and ioemu goes to /usr/local - great!
If you don't know a way how to make xen-setup to read the PREFIX make variable
from xen's build system, then my patch is the only way to go.
Christoph
--
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Karl-Hammerschmidt-Str. 34, 85609 Dornach b. Muenchen
Geschaeftsfuehrer: Thomas M. McCoy, Giuliano Meroni
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632
next prev parent reply other threads:[~2009-05-05 15:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-31 12:22 [PATCH] Fixes for build/install system Christoph Egger
2009-03-31 16:11 ` Ian Jackson
2009-04-01 7:44 ` Christoph Egger
[not found] ` <200904221037.00833.Christoph.Egger@amd.com>
[not found] ` <18927.13912.58144.792099@mariner.uk.xensource.com>
2009-04-22 15:46 ` [PATCH] ioemu: " Christoph Egger
2009-04-23 15:43 ` Ian Jackson
2009-04-23 15:54 ` Christoph Egger
2009-04-23 17:19 ` Ian Jackson
2009-04-24 6:34 ` Christoph Egger
2009-04-29 15:30 ` Ian Jackson
2009-05-04 9:42 ` Christoph Egger
2009-05-05 14:00 ` Ian Jackson
2009-05-05 14:15 ` Christoph Egger
2009-05-05 14:28 ` Ian Jackson
2009-05-05 15:25 ` Christoph Egger [this message]
2009-05-05 17:22 ` Ian Jackson
2009-05-08 9:29 ` Christoph Egger
2009-05-08 16:13 ` Ian Jackson
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=200905051725.16326.Christoph.Egger@amd.com \
--to=christoph.egger@amd.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=Keir.Fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.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.