Re: [Xen-devel] xen-unstable stubdom build-failure when debug=n

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Sat, 2014-07-26 at 17:14 +0200, Sander Eikelenboom wrote:
> Just tested some more with a strange outcome:
> 
> When doing:
> ~# git checkout  RELEASE-4.4.0
> ~# make mrproper && ./configure && make debug=n
> 
> It also fails with the error in dhcp i mentioned before.
> 
> However if i do:
> ~# git checkout  RELEASE-4.4.0
> ~# make mrproper && ./configure && make
> 
> It builds fine .. (and release-4.4.0 should have the implicit debug=n)
> So what is different when explicitly giving debug=n ?

The only thing I can thing of would be that specifying debug= on the
make command line makes it enter the environment or MAKEFLAGS or
something, whereas setting it in the Makefile or .config etc doesn't.
(Perhaps e.g. "export debug" in Config.mk would make these two behave
the same?)

Anyway, that having happened the debug could then filter down and get
picked up by the configure or build system of some sub-component in a
way we aren't expecting.

That's all 100% speculation though.

Ian.


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