From: "Jan Beulich" <jbeulich@novell.com>
To: John Levon <levon@movementarian.org>, Keir Fraser <keir@xensource.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Building broken with CS 13282
Date: Tue, 09 Jan 2007 08:25:15 +0000 [thread overview]
Message-ID: <45A35F7B.76E4.0078.0@novell.com> (raw)
In-Reply-To: <C1C84260.7492%keir@xensource.com>
>If there are dependencies among the auto-generated headers then they need to
>be listed explicitly. Multiple dependencies listed in a single rule can be
>made in parallel.
No, that's not the case - each header can be built independently, since the
#include-s are being substituted before handing to the preprocessor (not the
compiler, hence incomplete definitions don't matter), and substituted back
afterwards.
John, in order to understand what's wrong on your end I'll need more than just
the failing compiler invocation, specifically all the commands run while building in
xen/include (invoked from xen/Makefile:73). Since that's a series of $(MAKE)
invocations there, failure here should prevent making $(TARGET). Hence I
have to assume that something fails in the process of handling xen/include, but
doesn't indicate so through the process exit status (for that knowing what
actually got generated in xen/include/compat/ might also provide a clue).
Jan
next prev parent reply other threads:[~2007-01-09 8:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-08 10:49 Building broken with CS 13282 Christoph Egger
2007-01-08 11:07 ` Keir Fraser
2007-01-08 12:24 ` John Levon
2007-01-08 13:19 ` Keir Fraser
2007-01-08 14:13 ` John Levon
2007-01-08 14:30 ` John Levon
2007-01-08 14:40 ` Christoph Egger
2007-01-08 14:50 ` John Levon
2007-01-08 16:17 ` Keir Fraser
2007-01-08 17:26 ` John Levon
2007-01-08 18:48 ` Keir Fraser
2007-01-08 18:52 ` John Levon
2007-01-09 8:25 ` Jan Beulich [this message]
2007-01-08 12:20 ` Yu, Ping Y
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=45A35F7B.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=keir@xensource.com \
--cc=levon@movementarian.org \
--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.