From: Peter Zijlstra <peterz@infradead.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Fenghua Yu <fenghua.yu@intel.com>, Michal Marek <mmarek@suse.cz>
Subject: Re: [kbuild] Re: linux-next: build failure after merge of the tip tree
Date: Thu, 17 Feb 2011 13:45:47 +0100
Message-ID: <1297946747.2413.1717.camel@twins> (raw)
In-Reply-To: <20110217124304.GA27504@elte.hu>
On Thu, 2011-02-17 at 13:43 +0100, Ingo Molnar wrote:
> * Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> > Hi all,
> >
> > On Mon, 31 Jan 2011 15:42:59 +1100 Stephen Rothwell <sfr@canb.auug.org.au> 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.
Yeah, I run into this problem once every few days, totally annoying. A
make clean does fix it so I couldn't be arsed to actually submit myself
to Kbuild voodoo, but if someone who knows about that stuff could come
up with a fix I'd be most obliged.
next prev parent reply index
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-31 4:42 Stephen Rothwell
2011-02-17 3:47 ` Stephen Rothwell
2011-02-17 12:43 ` [kbuild] " Ingo Molnar
2011-02-17 12:45 ` Peter Zijlstra [this message]
2011-02-17 13:18 ` Michal Marek
2011-02-17 15:02 ` Michal Marek
2011-02-17 17:11 ` Ingo Molnar
2011-02-17 22:47 ` Stephen Rothwell
2011-02-18 3:54 ` Stephen Rothwell
Reply instructions:
You may reply publically 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=1297946747.2413.1717.camel@twins \
--to=peterz@infradead.org \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mmarek@suse.cz \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
/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
Linux-Next Archive on lore.kernel.org
Archives are clonable:
git clone --mirror https://lore.kernel.org/linux-next/0 linux-next/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 linux-next linux-next/ https://lore.kernel.org/linux-next \
linux-next@vger.kernel.org
public-inbox-index linux-next
Example config snippet for mirrors
Newsgroup available over NNTP:
nntp://nntp.lore.kernel.org/org.kernel.vger.linux-next
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git