From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756313Ab1BQMn0 (ORCPT ); Thu, 17 Feb 2011 07:43:26 -0500 Received: from mx2.mail.elte.hu ([157.181.151.9]:57042 "EHLO mx2.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756308Ab1BQMnV (ORCPT ); Thu, 17 Feb 2011 07:43:21 -0500 Date: Thu, 17 Feb 2011 13:43:04 +0100 From: Ingo Molnar To: Stephen Rothwell Cc: Thomas Gleixner , "H. Peter Anvin" , Peter Zijlstra , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Fenghua Yu , Michal Marek Subject: [kbuild] Re: linux-next: build failure after merge of the tip tree Message-ID: <20110217124304.GA27504@elte.hu> References: <20110131154259.dca1f7e6.sfr@canb.auug.org.au> <20110217144743.2db26b27.sfr@canb.auug.org.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110217144743.2db26b27.sfr@canb.auug.org.au> User-Agent: Mutt/1.5.20 (2009-08-17) X-ELTE-SpamScore: -2.0 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-2.0 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.2.5 -2.0 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Stephen Rothwell wrote: > Hi all, > > On Mon, 31 Jan 2011 15:42:59 +1100 Stephen Rothwell wrote: > > > > After merging the tip tree, today's linux-next build (x86_64 allmodconfig) > > failed like this: > > > > x86_64-linux-gcc: arch/x86/lib/memmove_64.c: No such file or directory > > > > Caused by commit 9599ec0471deae24044241e2173090d2cbc0e899 ("x86-64, mem: > > Convert memmove() to assembly file and fix return value bug") interacting > > with our build system. > > > > After removing arch/x86/lib/.memmove_64.o.cmd (left over from the build > > before merging the tip tree) from my object tree, it built correctly. > > I am still getting this (of course). You reported this as a -tip build failure - but it appears to be some sort of kbuild bug/artifact, right? There was a leftover .memmove_64.o.cmd file from an old tree. When jumping between kernel versions via git checkout a 'make mrproper' is generally needed. In most cases 'make' will figure things out but it's not always guaranteed. So for example there are version transitions where a stale include/asm links could cause build problems. Thanks, Ingo