All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: minios-devel@lists.xenproject.org
Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>,
	Wei Liu <wei.liu2@citrix.com>,
	xen-devel@lists.xenproject.org
Subject: Re: [PATCH v2] build: change MINI-OS_ROOT to MINIOS_ROOT
Date: Wed, 4 May 2016 10:27:23 +0100	[thread overview]
Message-ID: <20160504092723.GG2111@citrix.com> (raw)
In-Reply-To: <1462209995-24669-1-git-send-email-wei.liu2@citrix.com>

On Mon, May 02, 2016 at 06:26:35PM +0100, Wei Liu wrote:
> In the GNU make manual "How to Use Variables" section there is such
> word:
> 
> "However, variable names containing characters other than letters,
> numbers, and underscores should be considered carefully, as in some
> shells they cannot be passed through the environment to a sub-make (see
> Communicating Variables to a Sub-make)."
> 
> I discover xen stubdom fails to build on Ubuntu 16.04 and Debian
> unstable due to MINI-OS_ROOT is not preserved in the invocation of
> sub-make, while stubdom builds fine on older versions of Ubuntu and
> Debian. It's hard to track down what exactly is changed in those
> systems, but changing MINI-OS_ROOT to MINIOS_ROOT fixes the problem.
> 
> Signed-off-by: Wei Liu <wei.liu2@citrix.com>
> Acked-by: Samuel Thibault <samuel.thibault@ens-lyon.org>
> ---
> Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>
> Cc: xen-devel@lists.xenproject.org
> 

I've pushed this to mini-os.git master branch.

This is also a candidate to backport to 4.6 branch. I will wait a bit
before I actually do it.

Wei.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

      reply	other threads:[~2016-05-04  9:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-02 17:26 [PATCH v2] build: change MINI-OS_ROOT to MINIOS_ROOT Wei Liu
2016-05-04  9:27 ` Wei Liu [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=20160504092723.GG2111@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=minios-devel@lists.xenproject.org \
    --cc=samuel.thibault@ens-lyon.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.