xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Egger <Christoph.Egger@amd.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: [PATCH v2 4/4] tools/build: change order of config/Tools.mk inclusion
Date: Fri, 18 May 2012 13:52:15 +0200	[thread overview]
Message-ID: <4FB637EF.7080100@amd.com> (raw)
In-Reply-To: <20406.13989.715688.280631@mariner.uk.xensource.com>

On 05/18/12 13:46, Ian Jackson wrote:

> Roger Pau Monne writes ("Re: [PATCH v2 4/4] tools/build: change order of config/Tools.mk inclusion"):
>> Ian Jackson wrote:
>>> Also PREFIX is set in StdGNU.mk.  Why is it also set in Tools.mk ?
>>
>> Configure scripts have a very common option, --prefix, which is saved 
>> into Tools.mk as PREFIX, this is what should be used as prefix for 
>> installation.
> 
> I know that.  But given that the configure is just for the tools
> build, should we honour PREFIX from Config.mk (and ./.config or
> command line arguments) or from ./configure ?


The one from configure. The point is that the other path variables
also honour the prefix from configure.

Christoph

-- 
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Einsteinring 24, 85689 Dornach b. Muenchen
Geschaeftsfuehrer: Alberto Bozzo, Andrew Bowd
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632

  reply	other threads:[~2012-05-18 11:52 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-17 12:16 [PATCH v2 1/4] build/tools: disable libvchan build on NetBSD Roger Pau Monne
2012-05-17 12:16 ` [PATCH v2 2/4] autoconf: correctly parse *_INCLUDES and *_LIB env vars Roger Pau Monne
2012-05-17 12:16 ` [PATCH v2 3/4] python: set absolute path to libxl.h on _pyxl_types.c Roger Pau Monne
2012-05-17 13:25   ` Ian Campbell
2012-05-17 14:02     ` Roger Pau Monne
2012-05-17 14:38       ` Ian Campbell
2012-05-17 15:10         ` Roger Pau Monne
2012-05-17 15:14           ` Ian Campbell
2012-05-18  8:37             ` Christoph Egger
2012-05-18  8:41               ` Ian Campbell
2012-05-18  8:44               ` Roger Pau Monne
2012-05-18  8:41             ` Roger Pau Monne
2012-05-18  8:52               ` Ian Campbell
2012-05-18  9:14                 ` Roger Pau Monne
2012-05-18  9:25                   ` Ian Campbell
2012-05-18 11:13   ` Ian Jackson
2012-05-18 11:17     ` Roger Pau Monne
2012-05-17 12:16 ` [PATCH v2 4/4] tools/build: change order of config/Tools.mk inclusion Roger Pau Monne
2012-05-18 11:17   ` Ian Jackson
2012-05-18 11:29     ` Roger Pau Monne
2012-05-18 11:46       ` Ian Jackson
2012-05-18 11:52         ` Christoph Egger [this message]
2012-05-18 11:59         ` Roger Pau Monne
2012-05-18 13:30           ` Ian Jackson
2012-05-18 14:08             ` Christoph Egger
2012-05-22 14:48               ` Roger Pau Monne
2012-05-17 13:22 ` [PATCH v2 1/4] build/tools: disable libvchan build on NetBSD 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=4FB637EF.7080100@amd.com \
    --to=christoph.egger@amd.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=roger.pau@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).