From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: Building broken with CS 13282 Date: Tue, 09 Jan 2007 08:25:15 +0000 Message-ID: <45A35F7B.76E4.0078.0@novell.com> References: <20070108172634.GA10076@totally.trollied.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: John Levon , Keir Fraser Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org >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