All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: xen-devel@lists.xen.org,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	Ian Campbell <ian.campbell@citrix.com>,
	M A Young <m.a.young@durham.ac.uk>
Subject: Re: [PATCH] stubdom/Makefile should use QEMU_TRADITIONAL_LOC
Date: Fri, 24 Oct 2014 11:14:29 -0400	[thread overview]
Message-ID: <20141024151429.GB9938@laptop.dumpdata.com> (raw)
In-Reply-To: <20141024103641.GD15988@zion.uk.xensource.com>

On Fri, Oct 24, 2014 at 11:36:41AM +0100, Wei Liu wrote:
> On Fri, Oct 24, 2014 at 11:09:09AM +0100, M A Young wrote:
> > On Fri, 24 Oct 2014, Wei Liu wrote:
> > 
> > >On Thu, Oct 23, 2014 at 06:37:43PM +0100, M A Young wrote:
> > >>In http://xenbits.xenproject.org/gitweb/?p=xen.git;a=commit;h=8962a8f951ea83e8d10ee23aeb20266e4795b06e
> > >>CONFIG_QEMU was replaced by QEMU_TRADITIONAL_LOC in several places but not
> > >>in stubdom/Makefile, and as a result building stubdom is likely to fail when
> > >>xen-setup-stubdom isn't found. This patch replaces CONFIG_QEMU with
> > >>QEMU_TRADITIONAL_LOC in stubdom/Makefile as well.
> > >>
> > >
> > >While I understand the rationale behind this change, I'm a bit confused
> > >by the description. What does it mean by "is likely to fail"? Does it
> > >mean it succeeds sometimes and fails sometimes?
> > >
> > >What's your build setup? I'm wondering why this is not caught in
> > >OSSTest.
> > 
> > If OSSTest is setting CONFIG_QEMU explicitly then the build of stubdom will
> > work, as will everything else as QEMU_TRADITIONAL_LOC is set to the value of
> > CONFIG_QEMU (in Config.mk) if it exists. Nothing in the xen code sets
> > CONFIG_QEMU so if it isn't set explicitly stubdom/Makefile sets QEMU_ROOT to
> > . in stubdom/Makefile which isn't the right path for xen-setup-stubdom
> > (unless something is copying it over).
> > 
> 
> OSSTest doesn't set CONFIG_QEMU.
> 
> And looking at stubdom/Makefile, even if QEMU_ROOT is set to ".", the
> end result is still correct.
> 
> 347           ( $(buildmakevars2shellvars); \                                       
> 348             cd ioemu ; \                                                        
> 349             LWIPDIR=$(CURDIR)/lwip-$(XEN_TARGET_ARCH) \                         
> 350             TARGET_CPPFLAGS="$(TARGET_CPPFLAGS)" \                              
> 351             TARGET_CFLAGS="$(TARGET_CFLAGS)" \                                  
> 352             TARGET_LDFLAGS="$(TARGET_LDFLAGS)" \                                
> 353             $(QEMU_ROOT)/xen-setup-stubdom )      
> 
> Also xen-setup-stubdom is tracked in that repository, not copied from
> somewhere else. Probably worth checking what deleted it?
> 
> That said, I think this patch is correct and should be accepted as bug
> fix, because it's doing what 8962a8f951e did.

Release-Acked-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>

And Wei confirmed that his "is corret" is an Acked-by: Wei Liu <wei.liu2@citrix.com>

Thank you!
> 
> Only one minor comment on the commit message, can you use short commit
> hash with commit title instead of a URL to web git interface? Like
> 
> "In 8962a8f ("make: Normalize config options for external trees")
> CONFIG_QEMU was replace by ..."
> 
> Wei.
> 
> > 	Michael Young
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

  reply	other threads:[~2014-10-24 15:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-23 17:37 [PATCH] stubdom/Makefile should use QEMU_TRADITIONAL_LOC M A Young
2014-10-24  9:44 ` Wei Liu
2014-10-24  9:49   ` Ian Campbell
2014-10-24 10:09   ` M A Young
2014-10-24 10:36     ` Wei Liu
2014-10-24 15:14       ` Konrad Rzeszutek Wilk [this message]
2014-10-24 15:14 ` Wei Liu

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=20141024151429.GB9938@laptop.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=m.a.young@durham.ac.uk \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=wei.liu2@citrix.com \
    --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.