From: Ian Campbell <ian.campbell@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
Keir Fraser <keir@xen.org>, Doug Goldstein <cardoe@cardoe.com>,
Tim Deegan <tim@xen.org>
Subject: Re: [PATCH] Kconfig: fix environment variable handling
Date: Fri, 15 Jan 2016 15:44:29 +0000 [thread overview]
Message-ID: <1452872669.6020.46.camel@citrix.com> (raw)
In-Reply-To: <5696393302000078000C636E@prv-mh.provo.novell.com>
On Wed, 2016-01-13 at 03:46 -0700, Jan Beulich wrote:
> With xen/Makefile including include/config/auto.conf.cmd, environment
> variables checked in the latter must be available at the time of
> inclusion of that file, and hence must be populated in xen/Makefile
> rather than by passing to or inside xen/tools/kconfig/Makefile.kconfig.
> Otherwise incremental re-builds will always be full re-builds, which is
> not only annoying but actively problematic when building as non-root
> and only running "install-xen" as root.
>
> Also take the opportunity and remove stray $(Q) uses.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
>
> --- a/xen/Makefile
> +++ b/xen/Makefile
> @@ -20,6 +20,9 @@ MAKEFLAGS += -rR
>
> EFI_MOUNTPOINT ?= $(BOOT_DIR)/efi
>
> +ARCH=$(XEN_TARGET_ARCH)
> +SRCARCH=$(shell echo $(ARCH) | sed -e 's/x86.*/x86/' -e s'/arm\(32\|64\)/arm/g')
Why not just use XEN_TARGET_ARCH and TARGET_ARCH as defined in
xen/Rules.mk, at the point where recursing into kconfig/Makefile.kconfig?
Otherwise wouldn't we risk SRCARCH and TARGET_ARCH getting out of sync?
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-01-15 15:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 10:46 [PATCH] Kconfig: fix environment variable handling Jan Beulich
2016-01-13 15:50 ` Doug Goldstein
2016-01-15 15:44 ` Ian Campbell [this message]
2016-01-15 15:54 ` Jan Beulich
2016-01-15 16:01 ` Ian Campbell
2016-01-15 16:17 ` Jan Beulich
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=1452872669.6020.46.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=cardoe@cardoe.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 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.