All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juergen Gross <juergen.gross@ts.fujitsu.com>
To: Keir Fraser <keir.xen@gmail.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: xen-unstable: build fails
Date: Thu, 17 Mar 2011 09:59:54 +0100	[thread overview]
Message-ID: <4D81CD8A.9050601@ts.fujitsu.com> (raw)
In-Reply-To: <C9A772CD.14F43%keir.xen@gmail.com>

On 03/17/11 09:11, Keir Fraser wrote:
> On 17/03/2011 05:52, "Juergen Gross"<juergen.gross@ts.fujitsu.com>  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@ts.fujitsu.com
Domagkstr. 28                           Internet: ts.fujitsu.com
D-80807 Muenchen                 Company details: ts.fujitsu.com/imprint.html

  reply	other threads:[~2011-03-17  8:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-16 13:50 xen-unstable: build fails Juergen Gross
2011-03-16 14:45 ` Juergen Gross
2011-03-16 16:50 ` Keir Fraser
2011-03-17  5:52   ` Juergen Gross
2011-03-17  8:11     ` Keir Fraser
2011-03-17  8:59       ` Juergen Gross [this message]
2011-03-17 10:13         ` Jan Beulich
2011-03-17 10:29           ` Juergen Gross
2011-03-17 10:48             ` Jan Beulich
2011-03-17 10:55               ` Keir Fraser
2011-03-17 10:36         ` Keir Fraser
  -- strict thread matches above, loose matches on Subject: below --
2010-05-05  5:46 xen-unstable " Juergen Gross
2010-05-05  6:31 ` Shriram R
2010-05-05  9:00 ` Keir Fraser

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=4D81CD8A.9050601@ts.fujitsu.com \
    --to=juergen.gross@ts.fujitsu.com \
    --cc=keir.xen@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    /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.