xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
	xen-devel <xen-devel@lists.xenproject.org>
Cc: Ian Campbell <Ian.Campbell@eu.citrix.com>,
	Keir Fraser <keir@xen.org>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>
Subject: Re: [PATCH] fix qemu building with older make
Date: Mon, 28 Jul 2014 14:31:37 +0100	[thread overview]
Message-ID: <53D650B9.6000903@eu.citrix.com> (raw)
In-Reply-To: <53D6332002000078000267C3@mail.emea.novell.com>

On 07/28/2014 10:25 AM, Jan Beulich wrote:
> The $(or ) builtin (uses introduced by commits ffbf089357 and
> 8962a8f951) is supported only from make 3.81 onwards, yet we claim to
> only require make 3.80. Introduce a good enough fallback.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>

I don't really know enough about make to have an opinion on the code 
itself; but re the idea:

Acked-by: George Dunlap <george.dunlap@eu.citrix.com>

>
> --- a/Config.mk
> +++ b/Config.mk
> @@ -12,6 +12,7 @@ space   := $(empty) $(empty)
>
>   # fallback for older make
>   realpath = $(wildcard $(foreach file,$(1),$(shell cd -P $(dir $(file)) && echo "$$PWD/$(notdir $(file))")))
> +or       = $(if $(strip $(1)),$(1),$(if $(strip $(2)),$(2),$(if $(strip $(3)),$(3),$(if $(strip $(4)),$(4)))))
>
>   -include $(XEN_ROOT)/.config
>
> @@ -266,11 +267,11 @@ QEMU_TRADITIONAL_REVISION ?= d0395cc49b2
>   # QEMU_UPSTREAM_LOC ?= `pwd`/$(XEN_ROOT)/../qemu-xen.git
>
>   # Defaults for subtree locations
> -QEMU_TRADITIONAL_LOC ?= $(or $(wildcard $(QEMU_TRADITIONAL_INTREE)),\
> -                        $(QEMU_TRADITIONAL_URL))
> -
> -QEMU_UPSTREAM_LOC ?= $(or $(wildcard $(QEMU_UPSTREAM_INTREE)),\
> -                        $(QEMU_UPSTREAM_URL))
> +QEMU_TRADITIONAL_LOC ?= $(call or,$(wildcard $(QEMU_TRADITIONAL_INTREE)),\
> +                                  $(QEMU_TRADITIONAL_URL))
> +
> +QEMU_UPSTREAM_LOC ?= $(call or,$(wildcard $(QEMU_UPSTREAM_INTREE)),\
> +                               $(QEMU_UPSTREAM_URL))
>
>   # Short answer -- do not enable this unless you know what you are
>   # doing and are prepared for some pain.
>
>
>

  reply	other threads:[~2014-07-28 13:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-28  9:25 [PATCH] fix qemu building with older make Jan Beulich
2014-07-28 13:31 ` George Dunlap [this message]
2014-07-29 13:57 ` Ian Jackson
2014-07-29 14:22   ` Jan Beulich
2014-07-29 15:43     ` Ian Jackson
2014-07-29 16:13       ` Jan Beulich
2014-07-29 16:20         ` George Dunlap
2014-07-29 16:27           ` Andrew Cooper
2014-07-30  9:22         ` Ian Campbell
2014-07-30 10:22           ` Jan Beulich
2014-07-31 12:00           ` Don Slutz
2014-08-04 14:54             ` George Dunlap
2014-08-11 15:42               ` Don Koch
2014-09-01 10:41                 ` George Dunlap
2014-09-08 14:10                   ` Don Koch
2014-09-08 14:12                     ` George Dunlap
2014-09-08 15:11                       ` Don Koch
2014-09-08 16:51                       ` Pasi Kärkkäinen
2014-08-04 11:20 ` 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=53D650B9.6000903@eu.citrix.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=Ian.Campbell@eu.citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=keir@xen.org \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xenproject.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).