[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] xen-unstable: build fails


  • To: Keir Fraser <keir.xen@xxxxxxxxx>
  • From: Juergen Gross <juergen.gross@xxxxxxxxxxxxxx>
  • Date: Thu, 17 Mar 2011 09:59:54 +0100
  • Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Thu, 17 Mar 2011 02:01:19 -0700
  • Domainkey-signature: s=s1536a; d=ts.fujitsu.com; c=nofws; q=dns; h=X-SBRSScore:X-IronPort-AV:Received:X-IronPort-AV: Received:Received:Message-ID:Date:From:Organization: User-Agent:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=XveLAXBZlInj1QMz/wudjUsCIkFpwaA97uH95sV5eETlVL6fdfA8zmkX YecGhLSyzumWClR+KVIz/eikZ+SsHHfzVFv8fKL2LdtSxc7uZE5G+Q9Fz Az2Z4u4RDB0IQ38rrp7AhIHXVOSVIPMFHBmHtQnI7ezLl64rMI2L4Y7SF E8zWvlwfhJkDNTk5Rwq9n30WUJwRyBFoxZmV5c7V5ewCJDv5062lp1Ipd MucHmLk0gV44XhY+J+VUxrXXUiofR;
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

On 03/17/11 09:11, Keir Fraser wrote:
On 17/03/2011 05:52, "Juergen Gross"<juergen.gross@xxxxxxxxxxxxxx>  wrote:

The reason is clear: XEN_ROOT is set to a *relative* path. And when make is
including a Makefile, it switches the working directory to the directory of
the included Makefile. Including another Makefile via XEN_ROOT then is the
problem...

Well it's not clear to me. In my tests, including another Makefile does not
change the working directory, only recursive make with -C specified does
that. That seems logical -- pulling in standard rules containing wildcard
globs would otherwise have unpredictable results, if the wildcards were
evaluated in the directory of the included Makefile.

In your case, if Config.mk was getting run with incorrect relative XEN_ROOT,
how would the earlier include lines in that file work? You are getting an
error on '-include $(XEN_ROOT)/.config', but there are earlier (and
unconditional!) include lines in Config.mk that also reference XEN_ROOT. I
suppose they must be working.

So I think something is weird in your environment, or your make is broken.
However in this one specific failure case I can avoid redefining XEN_ROOT
outside xen/Makefile, since all hypervisor builds start at that Makefile. So
you can see whether c/s 23048 in xen-unstable staging fixes your build. I
applied it as it happens to be a teeny tiny cleanup as well.

We are both right :-)

I created /.config with:

$(warning /.config: $(MAKEFILE_LIST))

and got the following with "make tools":

make -C tools install
make[1]: Entering directory `/root/xen-unstable.hg/tools'
make[2]: Entering directory `/root/xen-unstable.hg/tools'
make -C check install
make[3]: Entering directory `/root/xen-unstable.hg/tools/check'
../../.config:1: /.config: Makefile ../../tools/Rules.mk ../../Config.mk ../../config/Linux.mk ../../config/StdGNU.mk ../../config/x86_64.mk /usr/include/../../.config


So the problem is not changing the working directory, but implicit directory
search. $(XEN_ROOT)/.config expands as ../../.config and this file was not
found, so make searches in /usr/include, as the file path is relative. And
/usr/include/../../.config results as /.config :-(

The problem is still the relative XEN_ROOT specification.
Or the missing .config under XEN_ROOT, so creating this file solves my
problem. :-)


Juergen

--
Juergen Gross                 Principal Developer Operating Systems
TSP ES&S SWE OS6                       Telephone: +49 (0) 89 3222 2967
Fujitsu Technology Solutions              e-mail: juergen.gross@xxxxxxxxxxxxxx
Domagkstr. 28                           Internet: ts.fujitsu.com
D-80807 Muenchen                 Company details: ts.fujitsu.com/imprint.html

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.