From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ingo Molnar Subject: Re: linux-next: build failure after merge of the final tree Date: Wed, 23 May 2012 17:35:36 +0200 Message-ID: <20120523153536.GD26974@gmail.com> References: <20120521185412.aca92107d0a8c4fdd8474e34@canb.auug.org.au> <20120521091257.GF31407@gmail.com> <20120522182542.655b939d96a8eb67390abb9a@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mail-wg0-f44.google.com ([74.125.82.44]:51690 "EHLO mail-wg0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755670Ab2EWPfr (ORCPT ); Wed, 23 May 2012 11:35:47 -0400 Content-Disposition: inline In-Reply-To: <20120522182542.655b939d96a8eb67390abb9a@canb.auug.org.au> Sender: linux-next-owner@vger.kernel.org List-ID: To: Stephen Rothwell Cc: Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Peter Zijlstra , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org * Stephen Rothwell wrote: > Hi Ingo, > > On Mon, 21 May 2012 11:12:57 +0200 Ingo Molnar wrote: > > > > * Stephen Rothwell wrote: > > > > > Hi all, > > > > > > After merging the final tree, today's linux-next build (i386 defconfig) > > > failed like this: > > > > > > Invalid absolute R_386_32 relocation: jiffies > > > > Hm, that's our fault: seems like a linker bug fallout, one which > > we fixed in -tip. > > > > > I am not sure what caused this (it may even been a bad merge > > > on my part). I have left it broken for today. > > > > While we've fixed this, to simplify merge window integration of > > linux-next I've excluded tip:x86/trampoline from the linux-next > > branch for now, so this build failure should go away tomorrow. > > Weirdly, I still got the same error today. Any ideas? Ought to be fixed now. Thanks, Ingo