xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "Keir (Xen.org)" <keir@xen.org>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	Jan Beulich <JBeulich@suse.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH 4 of 5] xen/makefile: Allow XEN_CHANGESET to be set externally
Date: Thu, 2 Aug 2012 14:47:07 +0100	[thread overview]
Message-ID: <501A84DB.3040101@citrix.com> (raw)
In-Reply-To: <20506.33289.314238.601890@mariner.uk.xensource.com>

On 02/08/12 14:35, Ian Jackson wrote:
> Andrew Cooper writes ("Re: [PATCH 4 of 5] xen/makefile: Allow XEN_CHANGESET to be set externally"):
>> # compile.h contains dynamic build info. Rebuilt on every 'make'
>> invocation.                                                                                                                                  
>>
>> include/xen/compile.h: include/xen/compile.h.in .banner
>>         @sed -e 's/@@date@@/$(shell LC_ALL=C date)/g' \
>>
>> So it should only be executed once (unless someone is messing around
>> deleting compile.h)
>>
>> Having said that, even if it were executed more than once, there is no
>> reasonable circumstance during which the contents of XEN_CHANGESET
>> should change.
> Uh, "hg up <changeset>", surely ?
>
> Ian.

Sure, but compile.h is regenerated on every invocation of Make

I should have stated that during an individual build there are no
reasonable circumstances.  Running an hg update during a build is asking
for trouble.

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

  reply	other threads:[~2012-08-02 13:47 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 [this message]
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

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=501A84DB.3040101@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 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).