All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: "Keir (Xen.org)" <keir@xen.org>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH 5 of 5] makefile: Use $(abspath) for XEN_ROOT
Date: Tue, 31 Jul 2012 18:36:16 +0100	[thread overview]
Message-ID: <50181790.6020600@citrix.com> (raw)
In-Reply-To: <501826420200007800091ADE@nat28.tlf.novell.com>

On 31/07/12 17:38, Jan Beulich wrote:
>>>> On 31.07.12 at 17:52, Andrew Cooper <andrew.cooper3@citrix.com> wrote:
>> This patch wraps the assignment of XEN_ROOT in each Makefile with a call to
>> $(abspath) which removes internal parent path references which result from 
>> the definition of XEN_ROOT as $(CURDIR)../../ (etc).
> Except that it's a make 3.81 invention, and so far we support
> building with make 3.80. So if you want to use it, you'll need to
> provide a fallback implementation (the placement of which may
> turn out to be problematic).
>
> Jan

Ah - so it is. 

Unfortunately, it appears hard to provide a backwards compatible way of
doing this.  Best to just forget this patch then, although it would be
nice to address this issue somehow in 4.3

~Andrew

>
>> For example, it changes the output from
>>
>>   gcc readnotes.o -o readnotes
>>   /bind/myrepos/xen-unstable.hg/tools/xcutils/../../tools/libxc/libxenctrl.so
>>   
>> /bind/myrepos/xen-unstable.hg/tools/xcutils/../../tools/libxc/libxenguest.so
>>
>> to
>>
>>   gcc readnotes.o -o readnotes 
>> /bind/myrepos/xen-unstable.hg/tools/libxc/libxenctrl.so
>>   /bind/myrepos/xen-unstable.hg/tools/libxc/libxenguest.so
>>
>> which decreases verbosity and increases clarity when reading the build log.
>>
>> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
>

-- 
Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer
T: +44 (0)1223 225 900, http://www.citrix.com

      parent reply	other threads:[~2012-07-31 17:36 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-31 15:51 [PATCH 0 of 5] Build system tweaks Andrew Cooper
2012-07-31 15:51 ` [PATCH 1 of 5] tools/ocaml: ignore and clean .spot and .spit files Andrew Cooper
2012-07-31 16:08   ` Ian Jackson
2012-08-01 11:47     ` Ian Campbell
2012-07-31 15:51 ` [PATCH 2 of 5] tools/config: Allow building of components to be controlled from .config Andrew Cooper
2012-07-31 16:10   ` Ian Jackson
2012-08-01 11:47     ` Ian Campbell
2012-07-31 15:51 ` [PATCH 3 of 5] config: Split debug build from debug symbols Andrew Cooper
2012-07-31 16:12   ` Ian Jackson
2012-08-01 11:47     ` Ian Campbell
2012-08-13 17:14   ` Ian Jackson
2012-07-31 15:52 ` [PATCH 4 of 5] xen/makefile: Allow XEN_CHANGESET to be set externally Andrew Cooper
2012-07-31 16:55   ` Ian Jackson
2012-08-01  7:49     ` Jan Beulich
2012-08-01  9:33       ` Andrew Cooper
2012-08-02 13:35         ` Ian Jackson
2012-08-02 13:47           ` Andrew Cooper
2012-07-31 15:52 ` [PATCH 5 of 5] makefile: Use $(abspath) for XEN_ROOT Andrew Cooper
2012-07-31 16:38   ` Jan Beulich
2012-07-31 16:54     ` Ian Jackson
2012-07-31 17:36     ` Andrew Cooper [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=50181790.6020600@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=keir@xen.org \
    --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.