From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Rothwell Subject: Re: linux-next: build failure after merge of the tip tree Date: Tue, 1 Mar 2016 20:40:01 +1100 Message-ID: <20160301204001.5594bed3@canb.auug.org.au> References: <20160301122910.74ff0a92@canb.auug.org.au> <20160301070750.GA6636@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: Received: from ozlabs.org ([103.22.144.67]:58802 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752076AbcCAJkJ (ORCPT ); Tue, 1 Mar 2016 04:40:09 -0500 In-Reply-To: <20160301070750.GA6636@gmail.com> Sender: linux-next-owner@vger.kernel.org List-ID: To: Ingo Molnar Cc: Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Peter Zijlstra , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Josh Poimboeuf Hi Ingo, On Tue, 1 Mar 2016 08:07:50 +0100 Ingo Molnar wrote: > > > This build is done with a PowerPC hosted cross compiler with no glibc. > > Ugh, what a rare and weird way to build an x86 kernel, and you made linux-next > dependent on it? It is just the fastest hardware I currently have access to (you remember who I work for, right? ;-)). I have always done at least part of the linux-next building (daily, or overnight) on PowerPC hardware and this is only the 2nd or third time in over 8 years that it has found an issue like this. > > I assume that some things here need to be built with HOSTCC? > > I suspect that's the culprit. Good, hopefully it is not too hard to fix. -- Cheers, Stephen Rothwell